maj/nextcloud-share
1
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases Wiki Activity

Configure git-flow workflow #4

New Issue
Closed
opened 2026-01-27 07:08:43 +00:00 by maj · 0 comments
maj commented 2026-01-27 07:08:43 +00:00
Owner
Copy Link

Initialize and document the git-flow workflow for the project. This includes setting up the main and develop branches, and documenting the branching strategy for features, releases, and hotfixes.

Tasks

  • Create develop branch from main
  • Push both branches to remote
  • Document branching strategy in CONTRIBUTING.md
  • Configure branch protection rules on Gitea (if available)

Branch Strategy

  • main - Production-ready releases only
  • develop - Integration branch for features
  • feature/* - New features (branch from develop, merge to develop)
  • release/* - Release preparation (branch from develop, merge to main + develop)
  • hotfix/* - Critical fixes (branch from main, merge to main + develop)

Acceptance Criteria

  • develop branch exists and is set as default
  • main branch represents production-ready code
  • Documentation clearly explains workflow
  • Team members understand branching strategy
Initialize and document the git-flow workflow for the project. This includes setting up the main and develop branches, and documenting the branching strategy for features, releases, and hotfixes. ## Tasks - [x] Create develop branch from main - [x] Push both branches to remote - [ ] Document branching strategy in CONTRIBUTING.md - [ ] Configure branch protection rules on Gitea (if available) ## Branch Strategy - `main` - Production-ready releases only - `develop` - Integration branch for features - `feature/*` - New features (branch from develop, merge to develop) - `release/*` - Release preparation (branch from develop, merge to main + develop) - `hotfix/*` - Critical fixes (branch from main, merge to main + develop) ## Acceptance Criteria - [x] develop branch exists and is set as default - [x] main branch represents production-ready code - [ ] Documentation clearly explains workflow - [ ] Team members understand branching strategy
maj added this to the Milestone 1: Project Infrastructure milestone 2026-01-27 07:08:43 +00:00
maj added the setuppriority:highinfrastructure labels 2026-01-27 07:08:43 +00:00
maj closed this issue 2026-01-28 18:13:34 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Bug fix
 bug
Bug fix
 ci-cd
Continuous integration/deployment
 ci-cd
Continuous integration/deployment
 configuration
Configuration management
 configuration
Configuration management
 core
Core functionality
 core
Core functionality
 developer
Developer-focused
 developer
Developer-focused
 distribution
Packaging and distribution
 distribution
Packaging and distribution
 docker
Docker/container related
 docker
Docker/container related
 documentation
Documentation updates
 documentation
Documentation updates
 epic
Epic/milestone tracking issue
 epic
Epic/milestone tracking issue
 feature
New feature
 feature
New feature
 gitea
Gitea-specific
 gitea
Gitea-specific
 infrastructure
Build, CI/CD, setup
 infrastructure
Build, CI/CD, setup
 integration
Integration between components
 integration
Integration between components
 library
Shared library code
 library
Shared library code
 networking
Network/HTTP code
 networking
Network/HTTP code
 platform:3ds
Nintendo 3DS specific
 platform:3ds
Nintendo 3DS specific
 platform:switch
Nintendo Switch specific
 platform:switch
Nintendo Switch specific
 platform:vita
PS Vita specific
 platform:vita
PS Vita specific
 platform:wiiu
Wii U specific
 platform:wiiu
Wii U specific
 priority:high
Must have for release
 priority:high
Must have for release
 priority:low
Nice to have
 priority:low
Nice to have
 priority:medium
Should have
 priority:medium
Should have
 security
Security-related
 security
Security-related
 setup
Setup and initialization
 setup
Setup and initialization
 status:blocked
Blocked by other issues
 status:blocked
Blocked by other issues
 status:in-progress
Currently being worked on
 status:in-progress
Currently being worked on
 status:review
In code review
 status:review
In code review
 task
Implementation task
 task
Implementation task
 testing
Testing and test infrastructure
 testing
Testing and test infrastructure
 ui
User interface
 ui
User interface
 user-facing
User-facing feature or documentation
 user-facing
User-facing feature or documentation
No Label infrastructure priority:high setup
Milestone
No items
No Milestone Milestone 1: Project Infrastructure
Projects
Clear projects
No project
Assignees
Clear assignees
maj
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: maj/nextcloud-share#4
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?