newrelic / newrelic/release-toolkit
Add `--excluded-dirs=.github` by default in all examples
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4
- Forks
- 9
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
One of the premises that leaded to this toolkit being born was that changes on non user-facing parts of a repository, such as build system, should not result in a new user-facing release.
However, as of now dependency bumps of github actions will result in a new release. An easy way to prevent this is to add the .github to excluded-dirs in generate-yaml.
Doing this by default is very tricky, so allegedly the best way to do so is to put it on every example we write.
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 by locating the repository's examples and the generate-yaml usage they contain. Update each example to include --excluded-dirs=.github, then verify that all examples consistently exclude the .github directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100