semantic-release / semantic-release/git
Why ".gitignore" is ignored ?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
Hi!
I'd like to understand the motivation for adding files that are ignored to the next commit.
For example, my project build outputs code into a dist folder. This should be published as part of the artifact on the registry.
But I don't want to find those dist files in the code (pollution IMO).
It seems like a common use case. Am I the only one troubled by this?
Thanks,
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
Read lib/git.js around line 19 and the linked commit to understand why ignored files are added to the next commit. Trace the release-asset flow and any related tests, then seek a maintainer decision on whether this behavior should change; the issue provides no acceptance criteria for a completed change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100