dmcfmnakkpmdfbcnpbjkfjmnbhkenaji
GitLab task organization helper with API integration A powerful GitLab enhancement extension that streamlines issue management and collaboration: ## Key Features - **Smart Assignment Management**: Easily assign and unassign issues with customizable quick-assign buttons for team members - **Priority Management**: Visual priority labels and quick-toggle system for better issue organization - **Designer View**: Toggle between developer and designer views for different workflow needs - **Enhanced Participants View**: Improved visibility of issue participants with larger avatars and quick-access controls - **Customizable Project Settings**: Configure per-project assignment rules and button labels - **Streamlined Comments**: Quick comment templates and improved comment form accessibility - **Label Management**: Better organization of labels with hide/show functionality ## Why Install? Perfect for teams using GitLab who want to: - Reduce clicks and streamline common actions - Improve issue tracking visibility - Customize their workflow per project - Better manage team assignments - Enhance collaboration between designers and developers
GitLab Open Locally
Open GitLab files locally in your IDE (also supports GitHub and Bitbucket) Chrome extension that opens GitLab(GitHub or Bitbucket) files directly in your local IDE (VS Code, Sublime Text, JetBrains IDEs, Windsurf, Vim, or custom). ✨ Features One-click opening - Click extension icon to open files instantly Multiple IDEs - VS Code, Windsurf, Sublime Text, JetBrains IDEs (PyCharm, IntelliJ IDEA, Rider, WebStorm, etc.), Vim (MacVim/Terminal/iTerm2), or custom IDE support Path mapping - Auto-detects local paths or use custom mappings Line number support - Jumps to the exact line you're viewing File history - Track last 5 opened files with quick mapping fixes Keyboard shortcut - Cmd+Shift+E (Mac) or Ctrl+Shift+E (Windows/Linux) Auto-save settings - No need to click save, everything persists automatically
GitBuddy.dev
Enhance GitHub PR reviews with AI-powered explanations. GitBuddy.dev is an AI-powered Chrome extension that supercharges your GitHub pull request (PR) workflow. It helps developers review code faster and more effectively with contextual code insights, AI-generated PR titles and descriptions, and an embedded AI chat assistant powered by state-of-the-art LLMs like GPT-4o and Claude. 🔧 How to use: 1. Visit gitbuddy.dev and create an account. 2. Install the GitBuddy Chrome extension. 3. Head over to any GitHub pull request. 🤖 Chat with a GPT-style assistant directly in the PR page for deeper insights, debugging help, or suggestions. It seamlessly blends into your GitHub workflow without requiring any manual setup in repositories.
GitGood
A collection of some helpful tweaks for GitHub - Add label buttons on the pull request list page - Track incomplete tasks in pull requests and alert - Display content at screen width in pull requests 1.0.1 - Improved to support older versions of the GitHub PR Timeline
bugzilla-github-extension
This extension integrates GitHub and Bugzilla Integrates Bugzilla and GitHub to make your life easier. It is a work in progress, so feel free to contribute: https://github.com/ditinc/bugzilla-github-extension - If GitHub Pull Request URL is populated with the pull request's URL, then a link will be added to the bug's title - There is a button for marking selected bugs as duplicates when changing several bugs at once - If the repository is associated with a Bugzilla product: - The Product will be listed under the repository name - There will be buttons to jump to Bugzilla lists of unresolved or resolved bugs - If the pull request's title includes the bug number (ex: 83513, [83513], Bug 83513, Bug85313) or if the branch contains the bug number (ex: bug_83513, Bug-83513, bug83513): - Bug number in title will be a link to the bug - Bugzilla section added to side listing some bug details - Comments will be sent to Bugzilla along with the Hours Worked entered in a new input added next to the comment buttons - This includes line comments, though they do not have an Hours Worked field - Have the option of setting but to RESOLVED FIXED when making a pull request comment - When creating a pull request, you have the option to: - Update the GitHub Pull Request URL on the bug in Bugzilla - Send the comment to Bugzilla - When merging a pull request, you have the option to: - Update the Code Status in Bugzilla - Update the bug to RESOLVED TESTED - Labels are pushed to the GitHub Labels field on the bug - If the release's comments include bug numbers (ex: 83513, [83513], [83513], [83513]): - Have the option of setting to In Staging or In Production in Bugzilla - Have the option of updating Release field in Bugzilla ... and more!
