Bringing internal fork features upstream#1494
Open
pjadhav-atlassian wants to merge 9 commits intomainfrom
Open
Bringing internal fork features upstream#1494pjadhav-atlassian wants to merge 9 commits intomainfrom
pjadhav-atlassian wants to merge 9 commits intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Is This Change?
• New token-based auth that reads from ~/.git-credentials
• Automatic token validation and refresh every 2 hours
• Thread-safe credential storage with mutex locks
• New command: "Authenticate with Bitbucket Token"
• New config: disableOnboarding to skip help screens
• New dependency: async-mutex for concurrency
• Auto-authentication on extension startup
• URI handler for deep-linking
• Respects onboarding configuration
• Less noisy error messages for missing commits
• Removed aggressive auto-focus on Bitbucket tree view
• Better .gitignore for patch directories
How Has This Been Tested?
Built and tested all basic functionalities.
Basic checks:
npm run lintnpm run testAdvanced checks:
Recommendations:
Ask your organization admin to add you to Rovo Dev Standard.
More about code review errors