-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger a build commit on push to master #41
Comments
Happy to set this up, but didn't know that was possible! Figured I needed to use the GitHub API to do any committing and pushing. Got docs for this handy? |
I don't have any experience with doing it in Travis myself (or with Travis in general), but you might find this Gist useful. The basic idea is to create a personal access token for authentication, but otherwise do your normal Git operations after setting Git's user details. You can see the Gist for details. As for invoking this only on |
I wonder if there is an equivalent in github actions through https://help.github.com/en/actions/reference/events-that-trigger-workflows. I just started playing around with this myself so it caught my eye. I am not too experienced myself with this either, but I wonder if there are certain advantages between both of these 😄 |
I saw a Travis CI config and thought that that was what was being used, but I see now that there are GitHub actions set up that actually do something. I'd recommend doing this with GitHub actions instead of Travis if that's what's being used. |
We don't check in |
Set up Travis CI so that when commits are pushed to the
master
branch, the project is built and the result is pushed back tomaster
. This should make pull request diffs easier to read and it will prevent branches from being polluted with "Build project" commits every time a change is requested.The text was updated successfully, but these errors were encountered: