About Git Helper for Azure DevOps

Git Helper is a Chrome Extension that adds productivity features directly inside Azure DevOps. Everything runs in your browser. No external server is involved except Azure DevOps and, optionally, AWS Bedrock.

Branch Toolbar

Features injected directly into the Azure DevOps branch list. No navigation required.

PR Creation

One-click PR creation

+ PR next to every branch. Creates a PR with title, description, and work items pre-filled. Inline Publish / Delete / View actions appear on success.

Draft mode

PRs are drafts by default. Toggle Create as Draft off in the popup to publish immediately.

Configurable targets

Set a default target branch (default: develop) and a separate one for develop source branches (default: main).

Auto-fill from branch name

Title and description generated from your branch name and commit history. Prefixes stripped, commits grouped by type. Merge commits and low-signal messages (wip, fix typo) excluded automatically.

Work item linking

Numeric IDs in the branch name (e.g. feature/12345/...) are linked to the PR automatically.

AI description generation

Connect AWS Bedrock to refine descriptions with AI. Disabled by default. Requires configuration in the popup.

Delete branch

Ownership-verified deletion

Delete button appears on your branches only, enabled once you are confirmed as the last committer. Inline Sure? confirmation prevents accidents.

Admin Delete

Enable in the popup to delete any non-protected branch regardless of ownership. Protected branches (main, master, develop, release) are always blocked.

Installation & Setup

Add to Chrome (free)

Opens Chrome Web Store — no account required to install

Step 1: Install from the Chrome Web Store

Click Add to Chrome, confirm the dialog, and the extension is ready. No restart required.

Step 2: Configure (click the toolbar icon)

Connection

Setting	Details
Personal Access Token (PAT)	Paste your Azure DevOps PAT. Required for PR creation and branch deletion. Required scope: Code: Read & Write. Click Test Access to verify. The extension detects your organisation from the active tab automatically.

+ PR Button: Configure ▾

Click Configure ▾ next to the + PR Button feature row to expand these options.

Option	Default	Details
Create as Draft	On	When on, new PRs are created as drafts. An inline Publish action appears after creation so you can publish without leaving the page. When off, PRs are published immediately and no Publish button is shown.
Default Target Branch	`develop`	The branch that PRs merge into for all source branches except `develop`. Change this if your team uses a different integration branch (e.g. `main` or `trunk`).
develop → Target Branch	`main`	Override for when the source branch is `develop` itself, typically used when merging a release up to `main`.
AI Description Generation	Off	When enabled, the generated PR description is sent to AWS Bedrock for AI enrichment before the PR is created. Toggling this on automatically opens the AI Configuration section. Has no effect if AI Configuration has not been saved.

Delete Branch: Configure ▾

Click Configure ▾ next to the Delete Branch feature row to expand this option.

Option	Default	Details
Admin Delete	Off	When off, the Delete button is only enabled on branches where you were the last committer. When on, the Delete button is enabled immediately for any non-protected branch regardless of ownership. Intended for repo admins cleaning up stale branches. Protected branches (`main`, `master`, `develop`, `release/*`) are always blocked.

AI Configuration: Configure ▾

Opened automatically when you enable AI Description Generation, or via Configure ▾ (appears after enabling AI in the + PR section). Powered by Amazon Bedrock.

Field	Details
AI Configuration toggle	Master on/off for AI. When off, no data is sent to Bedrock even if credentials are saved.
AWS Region	The AWS region where your Bedrock endpoint is provisioned. Default: `us-east-2`. The endpoint called is `bedrock-runtime.{region}.amazonaws.com`.
Model ID (optional)	Bedrock model to use. Leave blank to use the extension default (`anthropic.claude-3-5-sonnet-20241022-v2:0`).
Bearer Token	Your AWS Bedrock bearer token (ABSK). Stored locally only, never sent anywhere except `bedrock-runtime..amazonaws.com`. Click Test AI Connection* to verify credentials before saving.

Getting a PAT token

Go to dev.azure.com/{your-org}/_usersSettings/tokens
Click New Token
Scopes: Code → Read (add Write to also delete branches)
Copy the token and paste it into the extension popup

How + PR works

Click + PR next to any branch name (excluding main / master)
The extension derives a PR title from the branch name (strips prefixes, title-cases)
The target branch is determined from your popup settings, defaulting to develop or main when your source is develop
It fetches commits between your branch and the target, filters noise, and generates a structured description with Summary, Changes, and Testing sections
Any numeric IDs in the branch name (e.g. feature/12345) are included as work item links
If AI Description Generation is enabled and Bedrock is configured, the description is enriched before the PR is created
The PR is created via the ADO REST API. The page stays the same with inline actions appearing immediately
When Create as Draft is on: Publish, Delete, and View actions appear. When off: only Delete and View
If no PAT is configured, session cookies are used automatically

How branch deletion works

Deletes the branch from the remote repository for everyone. This is equivalent to git push origin --delete branch-name.

The Delete button is always visible next to non-protected branches, but starts disabled while ownership is checked
The extension identifies you via the ADO identity API using your PAT, then enables the button if you were the last committer
With Admin Delete enabled, the button is enabled immediately for any non-protected branch regardless of ownership
Protected branches (main, master, develop, release/*) are never deletable
Click Delete → an inline Sure? ✓ ✗ confirmation replaces the button
Click ✓ to confirm. The branch is deleted from the remote and removed from the list

Removing the extension

Go to chrome://extensions, find Git Helper for Azure DevOps, and click Remove. All locally stored settings are deleted with the extension.

Permissions Requested and Why

Git Helper requests only the minimum permissions required to provide its functionality.

Permission	User-facing feature	Why narrower is not viable
`storage`	Saves PAT token and AI settings (region, bearer token) to `chrome.storage.local` so they persist across sessions.	Without this permission, every setting resets when the browser closes. There is no narrower scope for local per-extension storage.
`activeTab`	Reads the URL of the currently active tab to detect which ADO organisation you are on (used to pre-fill the "Test against organisation" field in the popup).	Only the active tab URL is read. `tabs` permission (which grants access to all open tabs) is not requested.
`host_permissions`: `dev.azure.com/` `.visualstudio.com/*`	Injects the content script into Azure DevOps pages; calls the ADO REST API to fetch commits, branch refs, and user connection data; creates and deletes branch refs.	Content scripts and cross-origin fetch require host permissions matching the target origin. Narrower path patterns (e.g. only `/pullrequest/`) are not supported by Chrome's host permission syntax for content scripts.
`host_permissions`: `.amazonaws.com/`	Sends the generated draft and commit messages to AWS Bedrock for AI refinement, only when AI is enabled and a bearer token is configured. Only `bedrock-runtime.{region}.amazonaws.com` is contacted.	Chrome extensions cannot call cross-origin URLs from content scripts unless declared in `host_permissions`. If AI is disabled, this permission is never exercised.

No background permissions Git Helper does not use tabs, history, cookies, webRequest, bookmarks, identity, or any other sensitive Chrome API. It has no access to pages outside Azure DevOps.

Privacy Policy

Last updated: September 28, 2026

Overview

Git Helper for Azure DevOps is a Chrome Extension that adds PR workflow features to Azure DevOps pages. It is free to use for personal and commercial purposes. You may not copy, modify, redistribute, reverse-engineer, or create derivative works based on this extension. This policy explains what data the extension accesses, how it is used, and what leaves your browser.

Data Stored Locally

The following values are saved to chrome.storage.local, stored exclusively on your device and never transmitted to any server operated by this extension:

Personal Access Token (PAT): used to authenticate calls to the Azure DevOps REST API. Never sent anywhere other than dev.azure.com or *.visualstudio.com.
AWS Bedrock Bearer Token: your ABSK token for AI refinement. Never sent anywhere other than bedrock-runtime.*.amazonaws.com.
Settings: toggles, AWS region, AI model ID. Stored locally only.

Data Sent to Azure DevOps

The extension calls the Azure DevOps REST API to:

Create a PR (title, description, work item links) when you click + PR
Fetch commits between branches to generate the PR description
Fetch branch refs and committer identity for ownership checks
Delete a branch ref when you confirm a branch deletion

These calls are made directly from your browser to Azure DevOps using your configured PAT or existing session cookies. No intermediate server is involved.

Data Sent to AWS Bedrock

When AI is enabled and a PR is created, the extension sends to AWS Bedrock:

The selected commit messages
The PR title, source branch name, and target branch name
The template-generated draft description

No source code, file diffs, PAT tokens, API keys, or personal account information are included in the AI request. When AI is disabled, no data is sent to any AI provider.

Data Not Collected

Git Helper does not collect, transmit, or store:

Usage analytics or telemetry
Browsing history
Source code, file contents, or repository metadata beyond commit messages
Any data from pages other than Azure DevOps

Third-Party Services

The only external services the extension may contact are Azure DevOps (always) and AWS Bedrock (only when AI is enabled). No analytics, advertising, or tracking services are used.

Data Deletion

Remove the extension from Chrome to delete all locally stored data. You can also clear the extension's storage via chrome://extensions → Git Helper → Clear storage.

Contact

For questions about this Privacy Policy: lucamit@gmail.com

Terms of Service

Last updated: September 28, 2026

1. Acceptance of Terms

By installing or using Git Helper for Azure DevOps, you agree to these Terms of Service. If you do not agree, do not install or use the extension.

2. Description of the Service

Git Helper for Azure DevOps is a Chrome Extension that adds PR workflow features to Azure DevOps: one-click PR creation with auto-filled titles and descriptions, configurable draft mode and target branches, optional AI-powered description enrichment via AWS Bedrock, and safe branch deletion with ownership verification and an optional Admin Delete mode. It is intended as a productivity aid and should not be relied upon as the sole source of important PR documentation or as a substitute for reviewing your own changes.

3. Branch Deletion

The Delete branch feature permanently removes the branch from the remote repository for all users. You are solely responsible for any consequences of deleting a branch, including loss of work. Always confirm you no longer need a branch before deleting it. The developer is not responsible for data loss resulting from use of this feature.

4. License

Git Helper for Azure DevOps is free to use for both personal and commercial purposes. You may not copy, modify, redistribute, reverse-engineer, or create derivative works based on this extension or its source code without explicit written permission from the developer.

5. Third-Party AI Services

When AI refinement is enabled, commit data is sent to AWS Bedrock using the bearer token you provide. Your use of AWS services is governed by Amazon's terms. The developer of Git Helper is not responsible for the behaviour, outputs, data handling, pricing, or availability of AWS Bedrock.

6. No Warranty

Git Helper is provided "as is" without warranties of any kind. The developer does not guarantee that generated descriptions will be accurate, complete, or suitable; that the extension will remain compatible with future versions of Chrome or Azure DevOps; or that AI output will meet any quality standard. Always review generated descriptions before publishing them.

7. Limitation of Liability

To the maximum extent permitted by law, the developer is not liable for any damages arising from use of Git Helper, including inaccurate descriptions, data loss from branch deletion, service interruptions, or consequences of relying on AI-generated output.

8. User Responsibilities

You agree to use the extension only on repositories you are authorised to access, to comply with Azure DevOps and Chrome Web Store terms, and to review generated output before publishing.

9. Changes to These Terms

The developer may update these Terms at any time. Continued use after changes are posted constitutes acceptance of the revised terms.

Support

Getting help

See the Installation & Setup section above for configuration and usage guidance.

Report an issue

Email lucamit@gmail.com and please include:

What happened and what you expected
The Azure DevOps URL format (dev.azure.com or *.visualstudio.com)
Whether you are using a PAT or session auth
Whether AI is enabled and whether a Bedrock bearer token is configured
Any errors in the browser console (F12 → Console). Look for lines starting with [GH-ADO]