Skip to content

fix: skpackage v0.1.0: modify .github and .pre-commit-config.yaml. Follow new practices for writing commit/issue and news.rst file #160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bobleesj opened this issue Jan 2, 2025 · 1 comment

Comments

@bobleesj
Copy link
Contributor

bobleesj commented Jan 2, 2025

Please re-cookiecut but you would only need to modify the .github folder and .pre-commit-config.yaml. We’ve also added two group practices: For commit messages and issue titles, please use the guideline in Billingegroup/scikit-package#212. For writing news.rst, please use Billingegroup/scikit-package#227. Lastly, we are in the process of writing official documentation for bg-cookiecutter, which has also been cookiecuttered. So, please look out for that!

@bobleesj
Copy link
Contributor Author

bobleesj commented Jan 4, 2025

@Sparks29032 cookiecutter has been renamed to scikit-package to provide a name that is intuitive like that of pdffit2 and pdfgui. We may call "skpackage" or "package" as as a verb to communicate moving forward (we as a group will figure out the best together..)

Before re-package it, please update your local repository by running the command below:

git remote remove upstream
git remote add upstream https://github.com/Billingegroup/scikit-package

@bobleesj bobleesj changed the title fix: Cookiecut v0.1.0: modify .github and .pre-commit-config.yaml. Follow new practices for writing commit/issue and news.rst file fix: skpackage v0.1.0: modify .github and .pre-commit-config.yaml. Follow new practices for writing commit/issue and news.rst file Jan 4, 2025
@sbillinge sbillinge added this to the v0.2.0rc pre-release milestone Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants