MarketTakers/arbiter
6
0
Fork 0
Code Issues 14 Pull Requests 4 Packages Projects Releases Wiki Activity

Allow clippy's CI to automatically fix some of the linting issues #96

New Issue
Open
opened 2026-06-19 11:49:22 +00:00 by CleverWild · 0 comments
CleverWild commented 2026-06-19 11:49:22 +00:00
Member
Copy Link

roughly 60% of warnings can be fixed automatically, and it wins a lot of time.

There are three approaches to implementing automatic Clippy fixes in CI:

1. Direct Commit to PR

  • Pros: Fully automated; zero effort for developers.
  • Cons: High risk of git merge conflicts with local work.

2. Scheduled Bot PRs

  • Pros: Safe and predictable; allows a single, clean review of all fixes.
  • Cons: Doesn't fix active feature branches in real-time.

3. Chat-Ops Command

  • Pros: Total control; triggers only when a developer types a command (e.g., /clippy fix).
  • Cons: Requires extra setup and relies on manual triggers.
roughly 60% of warnings can be fixed automatically, and it wins a lot of time. There are three approaches to implementing automatic Clippy fixes in CI: ### 1. Direct Commit to PR * **Pros:** Fully automated; zero effort for developers. * **Cons:** High risk of git merge conflicts with local work. ### 2. Scheduled Bot PRs * **Pros:** Safe and predictable; allows a single, clean review of all fixes. * **Cons:** Doesn't fix active feature branches in real-time. ### 3. Chat-Ops Command * **Pros:** Total control; triggers only when a developer types a command (e.g., `/clippy fix`). * **Cons:** Requires extra setup and relies on manual triggers.
CleverWild added the
Kind
Enhancement
 label 2026-06-19 11:49:22 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat
Breaking
Breaking change that won't be backward compatible
Difficulty
High
3
Hard difficulty. Experience needed to fix: A lot.
Difficulty
Low
1
Easy difficulty. Experience needed to fix: Not much. Good first issue.
Difficulty
Medium
2
Medium difficulty. Experience needed to fix: Intermediate.
Kind
Bug
This is a bug.
Kind
Enhancement
Improve existing functionality.
Kind
Feature
New functionality
Kind
RFC
Request for comments
Kind
Security
This is security issue
Kind
Testing
This is testing issue.
Kind
Tracking issue
An issue tracking the progress of sth. like the implementation of an RFC
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Pending
4
Requires review by dev
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Kind
Enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
CleverWild Skipper Tangonell goodvin testuser
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MarketTakers/arbiter#96
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?