make-closed-issue

To automatically close a GitHub issue from recent commits, this workflow infers the scope of changes, generates a descriptive issue, commits relevant diffs with conventional messages, and closes the issue using the full commit hash. It then moves the issue to Done on the project board.

Yes, you can update a GitHub project board to Done automatically. After generating an issue and committing the relevant diffs, the workflow updates the Bitsocialnet project board, moving the newly created issue directly to the Done column.

Conventional commit traceability with GitHub issues works by generating a descriptive issue for recent changes, committing only relevant diffs using conventional commit messages, and closing the issue with the full commit hash to ensure a deterministic link between the work and the issue.

No, you do not need to manually calculate diffs. The workflow automatically calculates relevant diffs from recent changes, commits them with conventional messages to ensure deterministic behavior, and generates a descriptive GitHub issue for the completed work.

The best way to ensure traceability for completed work is to automate the workflow: generate a descriptive GitHub issue, calculate and commit only relevant diffs with conventional messages, close the issue using the full commit hash, and update the project board to Done.