Skip to content

Cleanup#7084

Open
BlackYps wants to merge 9 commits intodevelopfrom
cleanup
Open

Cleanup#7084
BlackYps wants to merge 9 commits intodevelopfrom
cleanup

Conversation

@BlackYps
Copy link
Copy Markdown
Contributor

@BlackYps BlackYps commented Apr 10, 2026

Description of the proposed changes

Some repo cleanup:

  • delete redundant changelog files: We use the files in docs/_posts as our source of truth, the old patchnotes files are not needed anymore.
  • improve comments on various workflow files
  • simplify the workflow that compiles the snippets
  • additionally the workflow now runs on the branch of a pull request to immediately test if the newly introduced snippet is working correctly. Previously it would run, but it would check out the develop branch, so you would only detect issues after the PR has been merged.

Testing done on the proposed changes

I tested that the changelog generation workflow still functions

Additional context

This is part of a bigger overhaul of the automation in this repo. More to come

No snippet because there are no changes that are relevant for the players

Checklist

@github-actions github-actions bot marked this pull request as draft April 10, 2026 18:13
@BlackYps BlackYps added area: documentation related to documentation to preserve knowledge and practices area: changelog management related to (automated) management of changelogs labels Apr 10, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 10, 2026

📝 Walkthrough

Walkthrough

Updated multiple GitHub Actions workflow references from test.yamltests.yaml; consolidated changelog pipeline into a single generate-changelog job and renamed its workflow input from referencebranch; adjusted docs, changelog snippets, and a helper script’s messages and templates accordingly.

Changes

Cohort / File(s) Summary
Workflow Reference Renames
/.github/workflows/deploy-faf.yaml, /.github/workflows/deploy-fafbeta.yaml, /.github/workflows/deploy-fafdevelop.yaml, /.github/workflows/stage-fafbeta.yaml, /.github/workflows/stage-fafdevelop.yaml
Updated test job uses target from ./.github/workflows/test.yaml./.github/workflows/tests.yaml; job wiring and dependencies unchanged.
Tests Workflow Display Name
/.github/workflows/tests.yaml
Renamed workflow display name from TestTests; no other logic changes.
Changelog Workflow Rework
/.github/workflows/docs-generate-changelog.yaml, /.github/workflows/docs-build.yml
Replaced separate verify and bundle jobs with a single generate-changelog job; changed input referencebranch; derive NAME from branch suffix for env/artifact naming; updated checkout/ref selection logic.
Documentation Updates
/.github/DEVELOPMENT.md, docs/development.md, docs/development-changelog.md
Updated act example and changelog documentation to reference tests.yaml and the renamed changelog workflow/input paths.
Changelog Snippets & Script Messages
changelog/snippets/sections/template-footer.md, changelog/snippets/sections/template-header.md, changelog/snippets/other.7084.md, /.github/workflows/scripts/bash/changelog-links.sh
Simplified contributor footer, ensured header newline, added other.7084.md snippet, and adjusted script header/comments/log messages (no functional behavior change).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Possibly related PRs

Suggested reviewers

  • Rhaelya

Poem

🐇 I hopped from test to tests with cheer,
One changelog job now gathers near,
Docs retold and links set right,
Templates trimmed and messages bright,
A little rabbit pranced — release is near!

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Cleanup' is vague and does not clearly convey the specific nature of the changes; it uses a non-descriptive term that could apply to many different types of work. Use a more specific title that highlights the main change, such as 'Rename test.yaml to tests.yaml and simplify changelog generation workflow' or similar.
Description check ❓ Inconclusive The PR description covers the main changes, testing, and context but does not include a changelog snippet despite acknowledging the template requirement. Although the author notes 'no snippet because there are no changes that are relevant for the players,' a changelog snippet was still created (other.7084.md). Clarify whether a snippet is needed or explicitly document why it's excluded from the checklist.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cleanup

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@BlackYps
Copy link
Copy Markdown
Contributor Author

The URL checker will pass again once this PR is merged

@BlackYps BlackYps force-pushed the cleanup branch 2 times, most recently from 5927fca to 1361ecd Compare April 11, 2026 20:18
@BlackYps BlackYps marked this pull request as ready for review April 11, 2026 20:24
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/docs-changelog.yaml (1)

59-65: ⚠️ Potential issue | 🟠 Major

Add repository parameter to checkout step for forked pull requests.

The Checkout snippets step (line 60–64) defaults to the base repository when the repository parameter is omitted. On forked PRs, github.head_ref references a branch in the fork, not the base repository, causing the checkout to fail.

Suggested fix
       - name: Checkout snippets
         uses: actions/checkout@v4
         with:
+          repository: ${{ github.event.pull_request.head.repo.full_name || github.repository }}
           path: fa
-          ref: ${{ inputs.branch || github.head_ref || github.ref_name}}
+          ref: ${{ inputs.branch || github.head_ref || github.ref_name }}
           sparse-checkout: |
             changelog/snippets
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/docs-changelog.yaml around lines 59 - 65, The "Checkout
snippets" step using actions/checkout@v4 fails on forked PRs because it omits
the repository parameter; update that checkout step (the step named "Checkout
snippets" which calls actions/checkout@v4 and currently sets path, ref and
sparse-checkout) to include a repository input set to the PR head repo (e.g. use
github.event.pull_request.head.repo.full_name with a fallback to
github.repository) so the action checks out the correct forked repository/branch
for pull requests.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/docs-build.yml:
- Around line 53-63: Update the reusable workflow references and documentation
to point to the real file name: change the `uses` values for the jobs
`changelog-develop` and `changelog-beta` from
`.github/workflows/docs-generate-changelog.yaml` to
`.github/workflows/docs-changelog.yaml`, and also update the link in
`docs/development-changelog.md` that references `docs-generate-changelog.yaml`
so it points to `docs-changelog.yaml`; ensure the `uses` entries remain relative
(same directory) and verify the job names `changelog-develop` and
`changelog-beta` still match the intended branches.

In @.github/workflows/docs-changelog.yaml:
- Around line 79-87: The step writes NAME to $GITHUB_ENV but then incorrectly
uses ${{ env.NAME }} in the same run and uses the wrong shell pattern; change
the run to compute REFERENCE and NAME with the shell using the last-path-segment
pattern (${REFERENCE##*/}), call changelog-combine.sh with the shell variable
(quoted as "$NAME"), and expose NAME to subsequent steps via env: NAME if
needed—avoid reading $GITHUB_ENV in the same run and stop using ${{ env.NAME }}
inside the run; reference the REFERENCE and NAME variables and the
changelog-combine.sh invocation when making the change.

---

Outside diff comments:
In @.github/workflows/docs-changelog.yaml:
- Around line 59-65: The "Checkout snippets" step using actions/checkout@v4
fails on forked PRs because it omits the repository parameter; update that
checkout step (the step named "Checkout snippets" which calls
actions/checkout@v4 and currently sets path, ref and sparse-checkout) to include
a repository input set to the PR head repo (e.g. use
github.event.pull_request.head.repo.full_name with a fallback to
github.repository) so the action checks out the correct forked repository/branch
for pull requests.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7925d1b0-eed0-47df-8603-3667f4ad1085

📥 Commits

Reviewing files that changed from the base of the PR and between 5bcb15a and fe2b3e8.

📒 Files selected for processing (14)
  • .github/DEVELOPMENT.md
  • .github/workflows/deploy-faf.yaml
  • .github/workflows/deploy-fafbeta.yaml
  • .github/workflows/deploy-fafdevelop.yaml
  • .github/workflows/docs-build.yml
  • .github/workflows/docs-changelog.yaml
  • .github/workflows/scripts/bash/changelog-links.sh
  • .github/workflows/stage-fafbeta.yaml
  • .github/workflows/stage-fafdevelop.yaml
  • .github/workflows/tests.yaml
  • changelog/snippets/sections/template-footer.md
  • changelog/snippets/sections/template-header.md
  • docs/development-changelog.md
  • docs/development.md

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/docs-generate-changelog.yaml:
- Around line 86-89: The inline GitHub expression used to set REFERENCE in the
run block is a script-injection risk; instead pass the branch/ref value via the
job's env and use only shell variable expansion in the script. Update the
workflow to define an environment variable (e.g., REFERENCE) in the step's env
and remove `${{ ... }}` from the run script, then compute NAME from that shell
variable and call changelog-combine.sh $NAME, ensuring only the shell variable
(REFERENCE) is expanded in the run content.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b486a379-3756-4e0b-b674-146bf65d4f5e

📥 Commits

Reviewing files that changed from the base of the PR and between fe2b3e8 and 76ecf24.

📒 Files selected for processing (1)
  • .github/workflows/docs-generate-changelog.yaml

@BlackYps BlackYps force-pushed the cleanup branch 2 times, most recently from b942406 to f5166e9 Compare April 11, 2026 22:12
@BlackYps
Copy link
Copy Markdown
Contributor Author

I recommend to view the commits individually when reviewing. It makes the changes easier to understand.

@BlackYps BlackYps requested a review from Garanas April 11, 2026 22:19
@BlackYps BlackYps mentioned this pull request Apr 12, 2026
3 tasks
@BlackYps BlackYps requested a review from lL1l1 April 12, 2026 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: changelog management related to (automated) management of changelogs area: documentation related to documentation to preserve knowledge and practices

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant