Skip to content

chore: update tooling versions - #29

Merged
cdunster merged 2 commits into
mainfrom
update-tooling-versions
Jun 4, 2026
Merged

chore: update tooling versions#29
cdunster merged 2 commits into
mainfrom
update-tooling-versions

Conversation

@cdunster

@cdunster cdunster commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Perform a nix flake update to update all of the binary tools used by this project, things such as git-cliff and cargo-semver-checks.

I have tested it locally with the docker containers.

I have also enabled the ENABLE_PUSH_CREATE_USER option in Gitea via the docker compose environment variable instead of copying the app.ini file, modifying, and then copying back to the container.

@cdunster cdunster self-assigned this Jun 4, 2026
@cocogitto-bot

cocogitto-bot Bot commented Jun 4, 2026

Copy link
Copy Markdown

✔️ 84c7ea0...e3aaddb - Conventional commits check succeeded.

@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 99de7b3c-c2ac-4382-8fb7-9b0b0738ea98

📥 Commits

Reviewing files that changed from the base of the PR and between 03c55c6 and e3aaddb.

⛔ Files ignored due to path filters (1)
  • flake.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • docker-compose.yaml
  • flake.nix
  • scripts/setup_git.sh
💤 Files with no reviewable changes (2)
  • scripts/setup_git.sh
  • flake.nix

Walkthrough

This pull request updates infrastructure and development configuration. The Gitea service in docker-compose.yaml gains an environment variable to enable automatic user creation on repository push actions. Separately, the initool package is removed from the Nix development shell dependencies. The changes also reflect removal of runtime setup logic that configured this Gitea setting through script-based container manipulation.

Suggested reviewers

  • ThetaSinner
  • jost-s
  • mattyg
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The title 'chore: update tooling versions' describes only the nix flake update portion but omits the significant Docker/Gitea configuration change that constitutes part of the changeset. Revise the title to reflect both major changes, e.g., 'chore: update tooling versions and streamline Gitea setup' or focus specifically on the primary change if tooling is not the main intent.
✅ Passed checks (4 passed)
Check name Status Explanation
Description check ✅ Passed The description accurately relates to the changeset, explaining the nix flake update, testing performed, and the Gitea configuration refactoring through environment variables.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ 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 update-tooling-versions

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.

Comment thread docker-compose.yaml
@cdunster
cdunster requested a review from a team June 4, 2026 15:15
Comment thread scripts/setup_git.sh
@cdunster
cdunster enabled auto-merge (rebase) June 4, 2026 15:49
@cdunster
cdunster merged commit 5040629 into main Jun 4, 2026
5 checks passed
@cdunster
cdunster deleted the update-tooling-versions branch June 4, 2026 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants