Menu
This question refers to this: https://github.com/features/actions
I have written a GitHub action to build my code and create a production bundle. I'd like to have that included into my repository by committing the changes to origin/master. This seems like an obvious feature for GitHub actions to have but I can't find it anywhere. How do I commit changes with a GitHub action and push them?
216
You can use this GitHub Action to commit changes made in your workflow run directly to your repo: for example, you use it to lint your code, update documentation, commit updated builds, etc...
Steps to trigger repository dispatches To do this, first create a personal access token. Verify that an action run is happening. Open up the Publish modal in a Plasmic project, and input the webhook above. Remove the Push To GitHub action in the Plasmic publish dialog.
GitHub Actions offers features that let you control deployments. You can: Trigger workflows with a variety of events. Configure environments to set rules before a job can proceed and to limit access to secrets.
GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.
GitHub Action for GitHub Push. The GitHub Actions for pushing to GitHub repository local changes authorizing using GitHub token. With ease: update new code placed in the repository, e.g. by running a linter on it, track changes in script results using Git as archive, publish page using GitHub-Pages, mirror changes to a separate repository. Usage
Update: Please see the following question/answer for full details about how to push changes back to the remote. Push to origin from GitHub action An alternative option is create-pull-request action. It will automatically commit changes to a new branch and raise a pull request for you to review the changes.
The GitHub Actions for pushing to GitHub repository local changes authorizing using GitHub token. mirror changes to a separate repository. Personal Access Token. Destination branch to push changes. Can be passed in using $ { { github.ref }}.
Before pushing changes, you should update your local branch to include any commits that have been added to the remote repository. If someone has made commits on the remote that are not on your local branch, GitHub Desktop will prompt you to fetch the new commits before pushing your changes to avoid merge conflicts.
Update: Please see the following question/answer for full details about how to push changes back to the remote. Push to origin from GitHub action
An alternative option is create-pull-request action. It will automatically commit changes to a new branch and raise a pull request for you to review the changes. I wrote a detailed explanation about it as an answer to another question here: https://stackoverflow.com/a/58004257/11934042
79
I found the stefanzweifel/git-auto-commit-action to be the best solution. It's really as easy as:
- uses: stefanzweifel/git-auto-commit-action@v4
One could, of course, tune the parameters, like commit message, file globs and many others.
44
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
