swiftlang / swiftlang/github-workflows
Version the workflows
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 115
- Forks
- 57
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
Even if we put #73 in place, we could tag or create release branches so that downstream "uses" of swift_package_test.yml specify a constant semvar version instead of always working off of main which is more susceptible to breaking.
For example: swiftlang/github-workflows/.github/workflows/swift_package_test.yml@v1.2.3
Looks possible to automate with certain marketplace actions like https://github.com/marketplace/actions/tag-release-on-push-action, but manually bumping as need may be sufficient
Contributor guide
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 reviewing .github/workflows/swift_package_test.yml and the related approach proposed in issue #73. Decide whether release tags or release branches best provide constant semver references, then verify that downstream uses can target a version such as v1.2.3 and that the chosen versioning process is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, swift
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100