prosegrinder / .github Goto Github PK

Enable stalebot on all repos.

Add standards for JavaScript projects:

• ESLint
• TypeScript
• GitHub Actions

• validate the old "python-poetry-x" workflows are not used anywhere anymore
  • python-pointofview
  • python-narrative
  • python-cmudict
  • python-syllables
  • python-prosegrinder
  • python-prosegrinder-restapi
• delete old "python-poetry-x" workflows
• rename workflow templates from "python-x" and "pypi-x" to "poetry-x"
  • pypi-publish
  • python-ci
  • python-release

Create default funding button(s): https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository

Python 3.7 is out of support and Python 3.12 is GA.

Update poetry-test.yaml accordingly.

Use auto-changelog to generate a change log:

auto-changelog --unreleased --tag-prefix v --latest-version <version-from-pipeline>

Add contact method to CoC for reporting potential violations.

Add standards / configs for Markdown. Used across all projects:

• markdownlint
• grammar / spell check
• GitHub Actions

Looking over comparable ways to do bump and release in node, looks like using the same approach as I used on my poetry / python projects is simplest. Also keeps the approach consistent across languages.

• annotatedtext
• annotatedtext-remark
• annotatedtext-rehype
• languagetool-service

Add commitize to poetry projects to ensure consistent commit messages and replace build, tag, release, publish pipeline.

• python-pointofview
• python-narrative
• python-cmudict
• python-syllables
• python-prosegrinder
• python-prosegrinder-restapi

See: https://docs.github.com/en/actions/learn-github-actions/sharing-workflows-with-your-organization

Reusable Workflows:

• Poetry
  • Lint
  • Test
  • Publish (Lint, Test, Bump Version, Publish)
  • CI (Lint, Test)
• NPM
  • Lint
  • Test
  • Publish (Lint, Test, Bump Version, Publish)
  • CI (Lint, Test)
• Dependabot Batcher
• Autoapprove PRs
• PR Conventional Commits Title

Starter Workflows:

• Dependabot Batcher
• Autoapprove PRs
• Poetry CI
• Poetry Bump & Release
• PyPi Publish
• NPM CI
• NPM Bump & Release
• NPM Publish
• PR Lint

Need basic guidelines for use across projects. Individual projects may have additional guidelines.

Add standards for Python projects:

• pylint
• black (style)
• pytest (unit testing)
• GitHub Actions

• python-pointofview
• python-narrative
• python-cmudict
• python-syllables
• python-prosegrinder
• python-prosegrinder-restapi
• annotatedtext
• annotatedtext-remark
• annotatedtext-rehype
• languagetool-service

use the following commit message:

ci: update dependabot commit messages [skip ci]

For References:

github-actions

  commit-message:
    prefix: "ci"
    include: "scope"

gitsubmodule

  commit-message:
    prefix: "fix"
    include: scope

pip\node\etc

  commit-message:
    prefix: "fix"
    prefix-development: "build"
    include: "scope"

See: https://stackoverflow.com/questions/43007471/how-to-migrate-npm-package-to-an-organization-scope