Double check reuse action
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
https://github.com/nextcloud/.github/pull/478#issuecomment-2556555950 was reverted on the templates repo, so we should check if we rather have to keep our own copy of the template (then we should rename it) or if we want a separate upstream template in the .github repo.
Andy also mentioned:
If you compile after merging to master you would need to run reuse download --all and commit the result of this as a post merge-to-main step
Might be something to check for our dist compile action.
@max-nextcloud Can you check that?
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
Review the reverted templates-repo change and the related .github repository discussion first. Check whether this repository should keep and rename its own template or use a separate upstream template, then examine the dist compile action and verify whether reuse download --all is needed after merging to main.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100