You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 16, 2024. It is now read-only.
Often PRs require one-time manual intervention, which cannot or should not be encapsulated into a Salt state. Currently, these are recorded in an ad-hoc fashion and can be easily forgotten, especially with a remote team. I'd like to make this better in a few parts with more consistent communciation:
Any commit requiring a migration task should use a 'saltfs-migration: ' tag in the commit message, e.g. 520adf2
Automation (homu? A saltfs-specific bot? Something existing?) will check for these tags in the commit messages on a PR; if any are found, then after merging add a comment to the PR containing a todo list with each tag as an item. It should also add a new S-needs-migration tag
Whoever runs the Salt highstate with those changes should check off the migration items when they are done, and then remove the tag (manually? via bot?).
Often PRs require one-time manual intervention, which cannot or should not be encapsulated into a Salt state. Currently, these are recorded in an ad-hoc fashion and can be easily forgotten, especially with a remote team. I'd like to make this better in a few parts with more consistent communciation:
S-needs-migrationtag