[GH-ISSUE #231] [Task] Design a branching strategy #119

Closed
opened 2026-03-23 20:32:09 +00:00 by mirror · 1 comment
Owner

Originally created by @MikeWallaceDev on GitHub (Jan 7, 2022).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/231

Originally assigned to: @MikeWallaceDev, @appflowy on GitHub.

There are several examples named in the document.

  • Git Flow
  • Github Flow
  • GitLab Flow
  • One Flow
Originally created by @MikeWallaceDev on GitHub (Jan 7, 2022). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/231 Originally assigned to: @MikeWallaceDev, @appflowy on GitHub. There are several examples named in the document. * Git Flow * Github Flow * GitLab Flow * One Flow
Author
Owner

@Xazin commented on GitHub (Oct 10, 2023):

With our way of working currently, and our release flow, we do not currently have a need for a branching strategy.

I'll close this for now until we have a need for a dedicated strategy.

When in doubt, use Git or GitHub Flow (compatible)

<!-- gh-comment-id:1755994261 --> @Xazin commented on GitHub (Oct 10, 2023): With our way of working currently, and our release flow, we do not currently have a need for a branching strategy. I'll close this for now until we have a need for a dedicated strategy. When in doubt, use Git or GitHub Flow (compatible)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#119
No description provided.