Skip to content

Commit 978f53f

Browse files
committed
Capitalize "actions" in "GitHub Actions"
1 parent 92a397b commit 978f53f

File tree

1 file changed

+2
-1
lines changed
  • content/blog/entries/automate-github-for-more-than-CI CD

1 file changed

+2
-1
lines changed

content/blog/entries/automate-github-for-more-than-CI CD/contents.lr

+2-1
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ The resulting release notes require no manual editing at release time, and has s
6767
6868
### Repository Normalization
6969
70-
Within a private repository of internal helper scripts, the CC technical team has a number of Github Actions which trigger python scripts to keep configuration standardized across our repositories. We casually call this process "repository normalization". One such script ensures that we use a standard set of GitHub labels across all of our projects. This consistency helps us do things like direct users to [open issues in need of assistance](https://github.com/search?q=org%3Acreativecommons+label%3A%22help+wanted%22+state%3Aopen&type=Issues) across the organization, or issues [good for first-time open source contributors](https://github.com/search?q=org%3Acreativecommons+label%3A%22good+first+issue%22+state%3Aopen&type=Issues). With GitHub actions, its easy to set up scheduled tasks with only a few lines of human-readable configuration. Here's the gist of running a python script daily, for example:
70+
Within a private repository of internal helper scripts, the CC technical team has a number of Github Actions which trigger Python scripts to keep configuration standardized across our repositories. We casually call this process "repository normalization". One such script ensures that we use a standard set of GitHub labels across all of our projects. This consistency helps us do things like direct users to [open issues in need of assistance](https://github.com/search?q=org%3Acreativecommons+label%3A%22help+wanted%22+state%3Aopen&type=Issues) across the organization, or issues [good for first-time open source contributors](https://github.com/search?q=org%3Acreativecommons+label%3A%22good+first+issue%22+state%3Aopen&type=Issues). With GitHub actions, its easy to set up scheduled tasks with only a few lines of human-readable configuration. Here's the gist of running a Python script daily, for example:
7171
7272
```yaml
7373
name: Example scheduled python action
@@ -139,6 +139,7 @@ Here's some smaller and simpler automations that can make a huge difference in y
139139
- [Automate security releases on Sentry](https://github.blog/2020-08-24-automate-releases-and-more-with-the-new-sentry-release-github-action/)
140140
- [Add reminders to issues and pull requests](https://github.com/probot/reminders)
141141

142+
142143
These examples are a small sample of the non-CI/CD capabilities of GitHub Actions. You can peek in the `.github/` directory of any of our open source repositories to see the actions we're using, and feel free to make an issue on any project if you have an idea for an automation of your own. As we increase the number and quality of integrations in our open source repositories, we may update this article or create follow-up posts with more examples.
143144

144145
If you're interested in learning more about GitHub Actions, GitHub has a wonderful [marketplace](https://github.com/marketplace?type=actions) of avaliable actionsn you can explore, and the [documentation for actions](https://docs.github.com/actions) is avaliable in several languages.

0 commit comments

Comments
 (0)