feat: automate creating PRs to push content updates for iamdeveloper.com #61
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for iamdeveloperdotcom ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
nickytonline
commented
Nov 6, 2022
| git commit -m "chore (automated): update blog posts" | ||
| git push origin main | ||
| fi | ||
| ./bin/pr-blog-posts.sh |
There was a problem hiding this comment.
It was easier to put this all in a script instead. Same for videos below. It could be one script and I pass in something to say video or blog post, but I'm keeping it simple for now and a little duplication isn't a biggie.
| id: commit | ||
| - name: Setup git config | ||
| run: | | ||
| git config user.name 'token-generator-app[bot]' |
There was a problem hiding this comment.
Required so that someone can be associated to the commit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Instead of pushing changes directly to main when updating blog posts or the streaming page for video content, a pull request (PR) is generated now that is auto-merged if any changes were committed.
This brings a few things with it:
Here is an example post merge of this PR if you want to see it in action. #63
Issues & Related Documents
Closes #60
Post merge I wrote a blog post about all this. See Automate and Auto-Merge Pull Requests using GitHub Actions and the GitHub CLI