summaryrefslogtreecommitdiff
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* Switch from setup.py to pyproject.toml (#1324)Waylan Limberg2023-03-221-2/+2
|
* Officially support Python 3.11 (#1313)Waylan Limberg2022-12-091-1/+3
| | | Python 3.11 was released 2023-10-02.
* Drop support for PY36Waylan Limberg2022-05-241-6/+8
| | | | | | | | Python dropped support on 2021-12-23. Our policy (#760) is to drop support on the next point release after Python does. * Remove py36 tests * Test multiple recent versions of pypy * Remove pep562 backport
* Add markdown-link-check github action.Waylan Limberg2022-05-052-11/+12
| | | | Replaces CLI action run through tox. Closes #1243.
* Support Python 3.10Waylan Limberg2021-11-161-6/+8
| | | Fixes #1124.
* Fix cache error in CIfacelessuser2021-08-041-1/+1
| | | | | If cache is desired, we should look into this in the future and do it properly.
* add cache to workflows using actions/setup-nodeOscar Dominguez2021-07-061-1/+2
|
* Add require_changelog workflow action (#1051)Waylan Limberg2020-10-231-0/+24
| | | | | | | | | | | | | This action checks that an update was made to any file in docs/change_log/ but only if changes were made to files in markdown/. Presumably, any changes outside of markdown/ do not affect the behavior and do not require a notation in the change_log. If the proper permissions are available, a comment is added to the PR informing the PR author that an update to the changelog is missing. However, any PR's from forks do not have permission on the pull_request event. Unfortunately, the pull_request_target event doesn't seem to work at all. However, as the action only attempts to add a comment on failure, we only get a failure in the correct conditions, even if the error message is related to auth.
* Bump version to 3.3.23.3.2Waylan Limberg2020-10-191-0/+30
|
* Add PY39 support and drop PY35 (#1026)Waylan Limberg2020-10-061-6/+5
| | | | Python 3.5 reached end-of-life on 2020-09-12 and Python 3.9 was released on 2020-10-05.
* Refactor fenced_code & codehilite options (#816)Waylan Limberg2020-06-231-1/+3
| | | | | | | | | | | | | | | | | | | | * Add `language-` prefix to output when syntax highlighting is disabled for both codehilite and fenced_code extensions. * Add `lang_prefix` config option to customize the prefix. * Add a 'pygments' env to tox which runs the tests with Pygments installed. Pygments is locked to a specific version in the env. * Updated codehilite to accept any Pygments options. * Refactor fenced code attributes. - ID attr is defined on `pre` tag. - Add support for attr_list extension, which allows setting arbitrary attributes. - When syntax highlighting is enabled, any pygments options can be defined per block in the attr list. - For backward compatibility, continue to support `hi_lines` outside of an attr_list. That is the only attr other than lang which is allowed without the brackets (`{}`) of an attr list. Note that if the brackets exist, then everything, including lang and hl_lines, must be within them. * Resolves #775. Resolves #334. Addresses #652.
* Allow checklinks check to fail.Waylan Limberg2020-05-221-0/+3
| | | | | | | | | | | | | | | There are too many random arbitrary failures with this check. We still want the check to run to ensure we don't introduce any new errors. However, the random errors on external URLs are frustrating, especcially when a different URL fails on each run. And then when the URL is checked manually, it is clearly good. If the tool provided a flag to limit the check to intenral URLs only (it doesn't), we wouldn't use that anyway because we do want to know when an extenral URL becomes invalid. Although, I suppose we could do two runs, one intenral and one external and only allow the external to fail. But that will have to wait until such a feature is added to the tool or we find a better tool.
* Add deploy workflow (#971)Waylan Limberg2020-05-211-0/+53
|
* Add push trigger to tox workflow. (#968)Waylan Limberg2020-05-181-2/+11
| | | | | * The build button/badge in the README now only points to push events so that an unmerged failing PR doesn't cause the build status to show as 'failing.' * Restrict node setup to checklinks env.
* Switch to GitHub Actions from Travis (#958)Waylan Limberg2020-05-091-0/+80