Create a GH workflow example, when PR merge registers a version / assigns a stage
Open
enhancement
product
- Dominant language
- Python
- Stars
- 162
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Some users may want to register new version / assign a stage to a specific artifact when PR is merged. This could be achieved by creating a GH workflow that does this. Few questions:
1. How to know which artifact to register? Which semver to use? Which stage to assign? (Maybe Labels? I've seen some tools that bump project's semver based on PR labels like `minor`, `major`, `patch`). What if there are multiple artifacts to register/assign stages to?
2. Should we add an example of this workflow in `gto-example` repo?
3. Does it influence GTO/DVC integration in any way?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.