Repository navigation
chore: Clarify GitHub Actions workflow names - #378
Conversation
The two cleanup workflows were easy to confuse: cleanup-previews.yml
("Cleanup PR Previews") removes Connect preview bundles, while
preview-cleanup.yml removes gh-pages docs previews. Rename both files
and give every workflow a descriptive display name.
jat255
changed the title
|
Preview deployed to Connect ( Deployed from commit 97fe360. |
|
Preview root: https://posit-dev.github.io/commons/pr-378/ Python site preview: https://posit-dev.github.io/commons/pr-378/py/ Built from the latest commit on this branch. The R links in it point at the published R site, which no pull request rebuilds. |
|
Preview deployed to Connect ( Deployed from commit 97fe360. |
jat255
added
r
|
Cleaned up 1 preview bundle(s) on https://dogfood.team.pct.posit.it: 371677 |
|
Cleaned up 1 preview bundle(s) on https://connect.staging.pct.posit.it: 2990 |
1 participant
The two cleanup workflows were easy to confuse: one removes Connect preview bundles, the other gh-pages docs previews. Renames them
connect-previews-cleanup.ymlanddocs-previews-cleanup.ymland gives every workflow a descriptive display name (several used their filename).py-release.yamlkeeps its filename: PyPI's OIDC publisher config names it.@simonpcouch tagging you as an FYI. This shouldn't have any impact other than renaming the actions, but I added prefixes to all the actions to make it easier to keep them straight. If you hate it, let me know and we can switch to something else.