owasp-modsecurity / owasp-modsecurity/ModSecurity
Exclude .gitignore files from release tarballs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
We import upstream releases in our own git repository, much like what happens with the debian packages on salsa.debian.org
Just noticed that we were missing some files due to .gitignore being shipped in the release files, which I don't think is actually needed.
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
No file or test is named. Start by locating the release tarball generation entry point and inspect how .gitignore files are included; confirm which files are currently missing from the imported archive. Done means generated release tarballs omit .gitignore files without omitting other required release files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100