eclipse-xtext / eclipse-xtext/xtext
Reduce maintenance via Renovate
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
I'm not part of the maintenance team, but it looks like part of the maintenance burden is dealing with dependency updates. On other projects, I am using Renovate to have updates pull-requested to me. With proper CI in place, I found that it is helpful with:
- automatically merging working updates, without having a human waste time
- have a clear indication of which is the first version of a dependency that is breaking the build
For instance, I realized thank to @HannesWell that I can circumvent #2686 in several of my use cases by simply forcing an update version of ASM. With Renovate in place, such update would have been pulled in automatically.
If the board believes this can be a way to go, I can help by providing a tailored configuration for the bot.
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
No files or tests are named. Start by reviewing the project's dependency and CI setup, then assess whether Renovate can support automated updates and merging; done would be an agreed, tested configuration tailored to this project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100