lightbasenl / lightbasenl/platforms
Tag release for the shared GitHub workflows
Open
Nobody has claimed this yet.
package: workflows
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Version bump tools currently try to bump to each commit on this repo. By tagging the workflows explicitly, we might be able to prevent that.
Some things to figure out:
- What tags are allowed?
- Do tools like dependabot understand
@workflow-name-v1.2->@workflow-name-v1.3or do they try to bump to in between versions of other releases?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the shared workflow definitions and reviewing how version bump tools currently resolve commits and tags. Determine which tag formats are allowed and test whether Dependabot understands transitions such as @workflow-name-v1.2 to @workflow-name-v1.3. Done means the tagging approach and its tool compatibility are documented clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100