Skip to content
Snippets Groups Projects

rules: introduce unreproducible sphinx cache file rule

Merged Jelle van der Waa requested to merge jelle/namcap:environment-pickle into master
1 unresolved thread

sphinx-build by default leaves unreproducible pickle files and other a cache files which should not be packaged.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
    • 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 really dislike this spec but I'll adhere to it if the majority likes it.

    • 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...

    • Please register or sign in to reply
  • added 6 commits

    Compare with previous version

  • added 1 commit

    • bc86218b - feat(rules): introduce unreproducible sphinx cache file rule

    Compare with previous version

  • added 3 commits

    Compare with previous version

  • Caleb Maclennan approved this merge request

    approved this merge request

  • Please register or sign in to reply
    Loading