Dispatch updates as patches to allow for modifications
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 24
- Forks
- 11
- Avg merge
- 13h 22m
- Merged PRs (30d)
- 15
Description
The workflows we distribute through this repo should be templates, not copies. Apps should have the ability to fine-tune them to their needs. Therefore it's tiresome if we always get PRs with fully replaced files where we have to hand-pick our changes on top of the new version. Example: https://github.com/nextcloud/contacts/pull/2620#r793584461.
So I'm proposing that ideally the dispatching of updates should apply them as patch, so that only the changed parts in this central repo are applied on the potentially modified copies. There will be conflicts where modifications are overwritten by updates, but in the happy case there is nothing to merge manually.
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 file, test, or entry point is named in the issue. Start by locating the code that dispatches workflow updates from this repository, then determine how it could apply changes as patches to modified copies; done should preserve local modifications where possible and expose conflicts for manual resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100