Skip to content

👷🏼 Implementation of canonical CI Workflows #12

@ccamel

Description

@ccamel

Purpose

Now the recent decision to hard fork the ichiban/prolog repository (refer to PR #11 and PR #9) is complete, we can apply our CI practices to ensure robust automation and streamline the development process of this repository.

Workflows to consider

(non exhaustive)

  • add-to-project.yml: Automatically adds new issues or pull requests to the project board.
  • auto-merge.yml: Automatically merges Dependabot pull requests when they pass all checks.
  • build.yml
    • build-go: Compiles the Go components of the project.
  • follow-contributor.yml: Automatically follows contributors who have made contributions.
  • lint.yml
    • lint-commits: Enforces commit message conventions.
    • lint-markdown: Ensures markdown files are clean and follow best practices.
    • lint-yaml: Validates YAML configurations for errors or inconsistencies.
    • lint-json: Ensures JSON files are correctly formatted.
    • lint-go: Lints Go code to ensure it follows style guidelines.
  • notify-release.yml: notify-discord: Sends notifications to our Discord server upon a new release.
  • release.yml
    • Jobs: Perform the release by tagging the repository and generating release notes.
  • test.yml
    • test-go: Executes unit tests for Go components.
  • thank.yml: Sends thank-you messages to contributors after their contributions are merged.

Additional Notes:

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

📆 To do

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions