OpenRefine / OpenRefine/CommonsExtension
Simplify release process with "release-please"
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 29
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
I recently discovered release-please which eases the release process by automating quite a lot of the tasks that we currently do manually. I would be keen to try out this tool and see if it could work for Wikidata-Toolkit, which has a fairly low traffic.
This would require adopting the "conventional commits" style of commit message:
fix:which represents bug fixes, and correlates to a SemVer patch.feat:which represents a new feature, and correlates to a SemVer minor.feat!:, orfix!:,refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
The migration to this release process would require merging https://github.com/OpenRefine/CommonsExtension/pull/131, as "release-please" doesn't handle the generation and upload of release artifacts by itself.
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 with the repository README's “how to make a release” section and review OpenRefine/CommonsExtension pull request 131, then compare those manual steps with release-please's requirements. Done means the project has an agreed release-please workflow, uses conventional commit categories, and can generate and upload release artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100