Github actions checkout1/29/2024 ![]() ![]() Unfortunately, cargo-release doesn't have a builtin way to do this, so we need to parse and increment the version manually. Create a new workflow, `Post-release version bump`, that should be run after a release and bumps version from `0.X.0` to `0.X+1.0-dev`. It is currently not associated with any account, but I feel this is still not appropriate here. We are using but according to ( ), that email address means "old no-reply email format for the user `bevy`". The crate filter is outdated now that we have more crates in `tools`. Most importantly, now that we are using `0.8.0-dev` in development, the workflow will try to bump it to `0.9.0` □ While playing with the code, I found some problems in the recently merged version-bumping workflow: No matter, thank you very much for the breakdown - an internet search landed me on this issue and your comment was exactly what I was looking for! I think this issue conversation, along with the "GitHub Actions bot email address?" conversation in the community forum is enough information for folks to figure out how to get the information needed to have the commit author show nicely on the GitHub interface.Īll that to say, I would also love to see this feature request implemented, as it would be nice for GitHub workflow authors. Searching GH for this shows there are currently over 7k+ workflows using this action, so it's also possible that there is a lot of 'copy&paste' workflow creation going on (I've done this myself, several times.) -> ![]() (Alternatively, GitHub's runners could be updated to use this - I don't know exactly where the user from your #3 is really coming from either, but I do see the below two GitHub Actions having examples using this 'user': If there is no caveat for the second option, I would suggest that the checkout action configures Git accordingly if none of both options is already set. The icon and name doesn't match what is usually shown for GitHub Actions. GitHub seems to link it to some user but clicking on the user opens a 404-page. Most repositories I found seem to use GitHub Action.I'm just wondering if there is any caveat since it is not promoted in the README.md. The author of the commit has the same icon and name as GitHub Actions everywhere else. A thread in the GitHub Support Community suggests github-actions.GitHub displays the author of the commit with the generic icon and without a link. However, this email is not recognized by the platform. The README.md suggests github-actions. ![]() I'm currently wondering which email address and username I should use for the time being. It would also lead to a more consistent appearance of commits created by GitHub Actions. Therefore, I think that this issue should be either closed or repurposed to account for the new feature in master. Nonetheless, even if keys were supported, I believe that setting the user and email would still be a side effect. This is because default tokens do not allow to update other repos while PATs provide too many permissions. Moreover, I think it would be desirable to support optionally using deployment keys instead of tokens (be it the default or a PAT). Using the token to do so is just another suitable solution. Explicitly setting the user and email would have been an approach. It seems to me that this issue was/is about " do other (authenticated) git operations" precisely update gh-pages (which was/is your " first use case for this"). The post-job step removes the token from the git config. Git config, which enables your scripts to run authenticated git commands. the rest will follow.Auth token used to fetch the repository. * ✨ seemless integration with cookiecutter. * □ test cookiecutter package as git repo * □ test if auto commit would commit something * □ test if auto commit would commit nothing or not github/workflows/moban-update.yml ad-m/github-push-action#38 ![]() * □ how could I about this without documentationgit add. * ✨ yes we need to use cookiecutter.extension.* steps: 1) git clone cookiecutter-pypackage 2) yh -c cookiecutter-pypackage 3) answer the quesetions 4) you will have what you wanted. yes, this code now can generate a cookiecutter package from cookiecutter-pypackage offline. * ✨ first ever pass on cookiecutter-pypackage. * ✨ auto-genenerate yehua file from cookie cutter json. * □ test cookie cutter, hello world project generation. * □ pytest requires the package to be installed by default * □ remove pyp圓 because it is based on python 3.5.3 * ✨ generate a hello world project from cookie cutter template on disk. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |