Skip to content

Card integration, task branches, and workflow improvements for enterprise use #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 11 commits into
base: develop
Choose a base branch
from

Conversation

euclidesgc
Copy link

Hello! How are you?

I'm submitting this PR to contribute some optional features that can help bring the extension closer to the workflow of large companies, especially those that use tools like Jira and have collaborative work processes.

Main points of the updates:

The new features are completely optional and do not change the default flow of the extension.
We implemented card integration for branch naming (feature, bugfix, hotfix, release, support, task) with a customizable template, making it easier to standardize and track with tools like Jira.
We added the concept of tasks, which are branches derived from a feature. This allows large features to be split into smaller tasks, enabling multiple developers to collaborate on the same feature at the same time—a common practice in Brazilian companies.
We included commands and configuration for managing these tasks within the Gitflow workflow.
We added options for offline work and sync checking, making the extension more flexible for different work environments.
We updated the Node.js version used in the project to 16.20.2.
Files created/updated/modified:

  • extension.ts
  • flow.ts
  • card.ts
  • config.ts
  • fs.ts
  • git.ts
  • fail.ts
  • package.json
  • tsconfig.json
  • README.md
  • CHANGELOG.md

The intention of these updates is to make the extension even more useful for teams that work collaboratively and are integrated with project management tools, without impacting those who prefer the traditional flow.

I'm available to discuss any points or make adjustments as needed. Thank you for your attention!


21 files changed
launch.json.vscode
settings.json.vscode
tasks.json.vscode
.vscodeignore
CARD_INTEGRATION_COMPLETE.md
CARD_INTEGRATION.md
CHANGELOG.md
Add Context...

New Features and Functionality:

  • Card Integration and Task Management:

    • Added support for card-based branch naming with customizable templates, enabling integration with project management tools. (src/card.ts, package.json) [1] [2] [3]
    • Introduced commands for starting and finishing tasks within the GitFlow workflow. (package.json)
    • Added configuration options for offline work and optional synchronization checks. (package.json)
  • Changelog and Documentation Updates:

    • Updated CHANGELOG.md and README.md to reflect new features, including card integration, task management, and offline mode. [1] [2]

Development Environment and Configuration:

  • ESLint and TypeScript Updates:

    • Added a new .eslintrc.json file with TypeScript-specific linting rules. (.eslintrc.json)
    • Updated package.json to use TypeScript 5.x, ESLint, and other modern dependencies. (package.json) [1] [2]
  • VS Code Configuration:

    • Updated .vscode/launch.json and .vscode/tasks.json for improved debugging and task execution workflows. (.vscode/launch.json, .vscode/tasks.json) [1] [2]
    • Added .vscodeignore to exclude unnecessary files from the extension package. (.vscodeignore)

Codebase Enhancements:

  • Improved Branch Naming Logic:
    • Implemented a CardIntegration class to handle card-based branch naming, validation, and formatting. (src/card.ts)
    • Fixed a minor issue in cmd.ts to ensure default return codes are set correctly. (src/cmd.ts)

These updates significantly enhance the extension's usability, maintainability, and compatibility with modern development practices.

@anhthang
Copy link
Owner

Thanks for your contribution. I will review and update soon

@anhthang
Copy link
Owner

anhthang commented Aug 9, 2025

Hi @euclidesgc

I was testing the feature and the task was created successfully with the following message:

Task branch task/verify created successfully from feature feature/card

However, I’m unable to finish the task due to the following error:

Invalid task branch format. Expected: task/feature-name/task-name

It seems the generated task branch name doesn’t match the expected format. Could you please check and fix this?

Thanks!

@anhthang anhthang changed the title Optional: Card integration, task branches, and workflow improvements for enterprise use Card integration, task branches, and workflow improvements for enterprise use Aug 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants