bgit v0.3 Post-Release Enhancements and Fixes
@rootCircle ci sta già lavorando.
Dal 9/6/2025.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
This issue tracks a collection of tasks aimed at improving bgit's stability, features, and user experience following the v0.3 release. These items focus on refining existing functionalities, integrating new capabilities, and addressing identified shortcomings.
Remaining Tasks:
-
Wrap
EnuminsideOptiontypes for operation modes in event:- Review existing
Enumusage and refactor instances whereOptionwould provide clearer semantics and better error handling.
- Review existing
-
Integrate and Utilize Rules:
- Implement and actively use the defined rules throughout
bgit's workflows to enforce best practices and ensure consistent behavior.
- Implement and actively use the defined rules throughout
-
Comprehensive Test Coverage:
- Develop and implement a robust suite of tests to ensure the reliability and correctness of all modules and workflows. This is a critical ongoing task.
-
Refactor Logging from
println!todebug!():- Replace all direct
println!statements within event handlers withdebug!()or other appropriate logging macros for more granular control over log verbosity and better integration with the logging framework.
- Replace all direct
-
Graceful Handling of
NoneDefaults:- Review code for instances where
Nonevalues are expected or possible, and implement graceful defaults or error handling instead of direct panics or errors.
- Review code for instances where
-
git pushForce Options: [SUPER HIGH PRIORITY]Investigate and implement support forgit push --force-with-leaseto provide a safer alternative togit push --force.Completely removegit push --force- done in #5
-
ta03_pop_stash- Supporting Other Indices:- (Future consideration) Extend the
ta03_pop_stashfunctionality to support popping stashes from specific indices, rather than just the most recent one.
- (Future consideration) Extend the
-
Fixing Credentials in Git Push/Pull: [SUPER HIGH PRIORITY]
- Address issues related to credential handling during
git pushandgit pulloperations, particularly concerning VSCode, SSH hiccups, and HTTPS authentication with GitHub rules.
- Address issues related to credential handling during
-
git cloneBehavior with.gitFolder:
Investigate and fix the issue where cloning a repository (e.g., linux.git) results in the creation of a directory that retains the .git suffix (e.g., linux.git instead of linux). The cloned repository should be placed in a directory without the .git suffix by default, mirroring standard Git behavior.fixed in #8
-
Fix
git_cloneEvent for Shallow Clones: [PRIORITY]- Ensure the
git_cloneevent correctly handles and executes shallow clones when requested.
- Ensure the
-
Merge Conflict and Branch Update Rule Implementation:
- Develop and implement rules specifically for detecting merge conflicts before add/commit and ensuring branch is up to date before pushing procedures.
-
Refine
raw_executeSignature:- Update the
raw_executefunction signature tofn raw_execute<T>(&self) -> Result<(bool, T), Box<BGitError>>to fix the leaky abstraction.
- Update the
-
Stacked Diffs Support:
- Explore and implement support for working with stacked diffs in bgit, which can enhance code review and development workflows.
-
Remove git usage from
Command:- Remove external git binary dependency in rules wherever possible. (eg: in no_secrets_staged)
-
Gitattributes based on file type being added and CRLF(EOL) defaults (detection and assignment)
- Lingua principale
- Rust
- Stelle
- 5
- Fork
- 1
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Issue simili
-
risk:low runtime status:in-progress type:test
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
zeroclaw-labs/zeroclaw#11023 ·
-
good first issue refactor
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
EricSpencer00/Resilient#4835 · 1 commento ·
-
agent:ready documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
cesarferreira/stax#890 ·
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100