You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose adding a feature in Sidekick that allows users to pin their Flutter environment to a specific commit, akin to the fvm use <commit-hash> command.
Current Functionality
Sidekick supports pinning to things like stable, master, and beta releases. However, it lacks the option to pin to a specific commit, requiring users to use terminal commands.
Proposed Feature
Pin to Specific Commit: Allow users to specify and pin their Flutter environment to a specific commit hash within SideKick.
Pin Current Master Commit: Option to pin the current head of the master branch, fixing the environment to a specific state of the master channel.
Use Case
Pinning to a specific commit ensures stability and consistency in team environments, preventing issues that arise from changes in the master channel. This is especially useful for utilizing fixes not yet in official releases.
Existing Behavior
Sidekick displays the pinned channel/hash but does not facilitate setting a specific commit in the interface. This requires terminal use, reducing convenience.
Benefits
Enhanced Stability: Mitigates risks from changes in the master channel.
Improved Convenience: Simplifies version management within Sidekick.
Better Team Coordination: Ensures uniformity across team environments.
Extending Sidekick’s functionality to support specific commits would enhance its usability and flexibility, benefiting users like me who need precise version control.
Thank you for considering this request.
The text was updated successfully, but these errors were encountered:
Description
I propose adding a feature in Sidekick that allows users to pin their Flutter environment to a specific commit, akin to the
fvm use <commit-hash>
command.Current Functionality
Sidekick supports pinning to things like stable, master, and beta releases. However, it lacks the option to pin to a specific commit, requiring users to use terminal commands.
Proposed Feature
Use Case
Pinning to a specific commit ensures stability and consistency in team environments, preventing issues that arise from changes in the master channel. This is especially useful for utilizing fixes not yet in official releases.
Existing Behavior
Sidekick displays the pinned channel/hash but does not facilitate setting a specific commit in the interface. This requires terminal use, reducing convenience.
Benefits
Extending Sidekick’s functionality to support specific commits would enhance its usability and flexibility, benefiting users like me who need precise version control.
Thank you for considering this request.
The text was updated successfully, but these errors were encountered: