* Update authors to "jrnl contributors" to comply with GPL3
* Include jrnl email address with contributors
* Include GPL notice in jrnl --version
* Apply consistent copyright and license to all Python files
* Add copyright and license to documentation
* Add copyright and license to docs theme
* Wiping poetry cache to try to resolve a test issue
* Testing with Python 3.9.0 in attempt to bypass GitHub Actions failure in 3.9.1
* make format
* Exclude Windows Python 3.9 build which is failing due to a GitHub Actions problem
* Modify testing to get around this 3.9 issue...
* Fix exclude
* remove old file that was only needed for gh-pages
* fix broken icons on docs home page
* add more contrast to twitter button hover state
* tweak non-accessible color to meet standard
* tweak non-accessible colors to meet standard
This new job will submit a PR to the relevant upstream repo as part of
the release workflow.
Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>
The changelog was triggering after each branch create on a repo. That
doesn't happen often on the main repo, but does happen often on
contributor forks. This should stop the rampant GH actions.
The previous plugin looked nice with the comments and annotations, but
apparently doesn't work for PRs. It can only run on the pr target (our
branch), which means that the tests are never actually run against the
new code.
As you can guess, this is pretty useless for PRs. So, this PR fixes
that, and uses the very nice pa11y-ci (instead of the normal pa11y).
While it doesn't upload annotations, the output is very readable and
seems like the best we're going to get.
Look, this might me my least ambitious commit ever, but having mismatched parentheses has crashed the internet before, so let's rather be safe than sorry!
This also unpins versions of some dependencies where the API is very
stable, or pinning wasn't getting us any additional stability.
Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>
Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>
* add some attribtutes to docs template for accessbility
* fix colors to meet accessibility guidelines (4.5 contrast ratio for text)
* Fix last remaining pa11y error (no button on search form)
This fix required moving the mkdocs theme out of the docs directory.
It's no in the docs_theme directory, and the mkdocs config is updated
accordingly.
* Re-enable accessibility testing for docs sit
Also, move the pa11y script into the gh actions workflow
* clean up linting issues in css
* fix and standardize link colors across site
* fix twitter button opacity making text fail contrast requirements
* move buttons on docs site index nav, tweak font weights
* fix footer opacity, tweak spacing of the now more visible sections of the page
* change font sizes on index page to meet WCAG
* udpate font sizes site-wide for accessibility
* fix sidebar for accessibility (font sizes and color contrasts)
* restyle code blocks to have dark background, and meet accessibility requirements
* standardize (accessible) colors across docs site
* Fixes for new CI pipeline (Github Actions)
- Support ci skip tag on commits to avoid build dupes
- Add smarter path detection so we don't spam tons of tests
- Allow steps to cancel if previous steps were cancelled (don't always
run)
- Separate workflows to be more modular
- Update release workflow to do a few more things
- Add helpful messages
- Be more strict in version checking (now with added regex)
- Make changelog smarter about when to trigger
- Add some functionality for changelog to handle releases and
prereleases separately
- Better error handling
- Split up the version validation and the release to make way for more
releases
* add step in workflow to merge to release branch after a release
* add check for git diff so commit doesn't error out constantly
* add bot token since gh actions doesn't allow pushing to protected branch
* add a max for issues, since we keep getting rate limited
* add jrnl bot username to commit step
* change token for git repo
* Add changelog workflow to github actions, remove old script
This basically takes the exact script, and turns it into a workflow. The
only difference is that the new workflow doesn't detect a release build
like the script did (releases will be a separate workflow).
* remove old config file for changelog generator (it's in workflow now)
* whitespace change
* remove ableist language
* Add initial config to test github actions
* remove other CI configs so PR doesn't get bogged down
* add poetry
* skip failing test, update behave output
* add multiple python versions
* add test cache
* try to use matrix for python version
* try to cache pip installation
* add other OSes
* whitespace changes
* skip failing test on windows
* add pip cache
* take out pip cache
* clean up, add linting steps
* add release branch to testing
* clean up
* add initial a11y config for docs site
* take out junit for now
* add junit annotations
* try different junit reporter
* add junit annotations into same workflow
* linter fix
* make junit step always run
* more junit
* clean up
* disable a11y exit code for now (always pass)
* put back travis and circle so we can temporarily run everything in tandem
* fix for issues with secret tokens
