-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add in a GENERAL_INFO.md
document?
#37
Comments
yeah, and it should probably replace https://pysal.org/docs/devs/ with the latest conventions (and maybe we leave this kinda developer documenting to here instead of the website so we dont get competing resources?) |
Seems like a reasonable idea. |
I would personally update https://pysal.org/docs/devs/ with such an info rather than creating another place for it. |
Agree we should have a single source, but i'd rather re-canonize it here. To me, the website feels like a place for users more than developers, whereas the submodule contract is where it makes more sense to house the 'dev set up' instructions. Right now both the submodule template and the website contain competing instructions, so i vote here rather than there. Tbh, i forget the website instructions even exist--but maybe thats just me. No worries if im outvoted |
I don't mind where is it, but agree that there should be only one source of truth. Could be here. |
We should maybe add some sort of file in the top level for general information, etc. like:
versioneer
usage and set uppre-commit
set upgh-pages
branchcondaforge-feedstock
and auto-merge (xref Automated merging for conda-forge feedstock #31)Maybe a file like
GENERAL_INFO.md
, where we make it clear that the file should be deleted when setting up an actual repo.The text was updated successfully, but these errors were encountered: