rules: introduce unreproducible sphinx cache file rule
sphinx-build by default leaves unreproducible pickle files and other a cache files which should not be packaged.
Merge request reports
Activity
added 4 commits
-
67815c3b...7d2e36db - 3 commits from branch
pacman:master
- bf11b86a - rules: introduce unreproducible sphinx cache file rule
-
67815c3b...7d2e36db - 3 commits from branch
added 1 commit
- 17d411e0 - rules: introduce unreproducible sphinx cache file rule
- Resolved by Jelle van der Waa
Just FYI I'm following the conventional commits spec for commit messages with the ultimate goal of using
git-cliff
for release notes. I've reworded your commits in other recent MRs and can fix this on on merge too, just noting for future...I have a love/hate relationship with it myself. I definitely don't use it on many personal projects that don't have public releases. At the same time for projects with public releases I've come to really like the ease of shipping with good release notes without any extra work at release time. Hence my request here. As the one cutting releases I much prefer to do the work up front of curating messages along the way...
added 6 commits
-
17d411e0...1073233f - 5 commits from branch
pacman:master
- 81bb4228 - rules: introduce unreproducible sphinx cache file rule
-
17d411e0...1073233f - 5 commits from branch
added 1 commit
- bc86218b - feat(rules): introduce unreproducible sphinx cache file rule
added 3 commits
-
bc86218b...d114edfe - 2 commits from branch
pacman:master
- 7cb57186 - feat(rules): introduce unreproducible sphinx cache file rule
-
bc86218b...d114edfe - 2 commits from branch