MetPy
MetPy copied to clipboard
More GitHub Actions
I've been brain-storming other ideas for types of automation we could add/handle here. Capturing here rather than in a random note in my private app:
- [x] Handle new versions of docs being added--likely using the
page_build
event- Update symlink for latest docs
- Automatically update
versions.json
- [ ] When a PR is merged, automatically add any linked issues to the next milestone
- This needs some way to automatically identify linked issues--there's no API currently
- [ ] Automatically update
AUTHORS.txt
upon PR merge (#383)- Might want to look at something like this to streamline: https://github.com/peter-evans/create-pull-request
- [ ] Comment-based bot to rebase a PR?
- https://github.com/cirrus-actions/rebase
- [ ] Automate bumping minimum dependencies?
- [x] ~Look at https://github.com/actions/create-release for release automation instead of all hand-rolled API~ Unmaintained and we have replaced with the automatically generated release notes.
- [ ] Label PRs based on changed paths: https://github.com/actions/labeler
- [ ] Label PRs based on labels for mentioned issues?
- [ ] Start using Projects for cross-milestone efforts (e.g. dask)--automate moving cards using actions
- [ ] Declarative labels so we can easily sync across projects
- https://github.com/lannonbr/issue-label-manager-action
- https://github.com/micnncim/action-label-syncer
- [ ] Better uploading coverage to Code Climate: https://github.com/paambaati/codeclimate-action
- [ ] Look at making more proper workflows, where there are jobs depdendent on each other
- Build docs -> (1) Link check (2) Upload
- actions/download-artifact
GitHub Pages can now directly be deployed using GitHub actions:
- One action to upload a full
.tar.gz
artifact of the site - Another to deploy to Pages
One challenge to being able to completely eliminate the gh-pages
branch is that to maintain the versioned docs, especially for older versions, we still need a copy of that static content somewhere--and a GitHub branch is one of the easiest ways to do so.
This could be used, at a minimum though, to eliminate the need to commit dev docs to the gh-pages
branch, and instead build on top of the gh-pages content and deploy directly.