New docs and automation, more modernization #19
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Stephen L Arnold <[email protected]>
* update/simplify setup and packaging files, migrate tool configs * add versioningit to build deps, update __init__.py * remove readme doc processing, prep for readme conversion * global import cleanup, add isort tox cmd * update .pre-commit-config.yaml and coverage.yml Signed-off-by: Stephen L Arnold <[email protected]>
Signed-off-by: Stephen L Arnold <[email protected]>
* add new tox commands for 'docs' and 'docs-lint' * cleanup link errors found by docs-lint * add sphinx doc build workflow, update ci workflow * remove new version var from __init__.py globals Signed-off-by: Stephen L Arnold <[email protected]>
Signed-off-by: Stephen L Arnold <[email protected]>
* add pylint badge workflow and update readme (docs-lint will fail until badge is created on PR merge) Signed-off-by: Stephen L Arnold <[email protected]>
* docs-lint will not pass without the link to pylint badge (which does not yet exist upstream) Signed-off-by: Stephen L Arnold <[email protected]>
* update conda recipe, needs version dep in host and run * cleanup setup.cfg and manifest files Signed-off-by: Stephen L Arnold <[email protected]>
* work-around for import error in github project source dir Signed-off-by: Stephen L Arnold <[email protected]>
* pypi action step is not fully enabled yet, requires setup * check pre-release packaging artifacts for sdist/bdist * start capturing rst CHANGES file from v0.6.0 onwards Signed-off-by: Stephen L Arnold <[email protected]>
* create changes file: gitchangelog v0.6.0.. > CHANGELOG.rst * edit top line in CHANGELOG.rst using current date/new tag * edit conda/meta.yaml using new tag, then tag this commit Signed-off-by: Stephen L Arnold <[email protected]>
* using release workflow to publish pypi packages needs first-time setup * first see the upstream readme for how to setup the token secret * then uncomment the publish step in release.yml and commit https://github.com/pypa/gh-action-pypi-publish * finally push a tag and wait.... Signed-off-by: Stephen L Arnold <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a combination of modernization/cleanup and new/updated tox and Github workflows:
_version.pydocs-lintin sphinx workflow