Infrastructure/Git/Simple Workflow: Difference between revisions

Latest revision as of 02:05, 21 February 2025

This article or section is out of date.
Reason: This page that shows up high in search results in 2025 was last updated in 2016 and marked "THIS IS AN INCOMPLETE DRAFT!!!". Instead read Infrastructure/GitLab. (Discuss in Talk:Infrastructure/Git/Simple Workflow)

View history if you want to see what it said, but don't bother discussing it.

@@ Line 1: / Line 1: @@
-== Simple KDE Git Workflow ==
+{{Out of date|This page that shows up high in search results in 2025 was last updated in 2016 and marked "THIS IS AN INCOMPLETE DRAFT!!!". Instead read '''[[Infrastructure/GitLab]]'''.}}
-This Git Workflow is designed to be followed by a new Git user who needs a simple workflow for bug fixes and new features in a manner similar to the old SVN workflow.
+:''View history if you want to see what it said, but don't bother discussing it.''
-Note that each module may choose to adopt a more complex workflow and you should check with your modules maintainers if this is the case.
-The worked examples given will be for an imaginary app called KFoo in a git.kde.org repository called 'kfoo'.
-== Set-up ==
-This section documents how to set you Git and you repository for development.
-=== Configure Git ===
-Follow the [[Infrastructure/Git/Configuration|KDE Git Configuration]].
-=== Clone your repository ===
-You need to clone your repository
-== Basic Actions ==
-This section documents basic actions that are performed within your workflow.
-See also the [[Infrastructure/Git/Recipes|KDE Git Recipes]] page.
-=== Create a Work Branch ===
-=== Commit Your Changes ===
-=== Push Your Changes ===
-== Local Bug Fixing ==
-This example workflow is for locally fixing bugs in stable and unstable branches and pushing them to the central repository.
-This workflow is only recommended for small fixes or where you are the only developer on a project.
-== Local Feature Development ==
-This example workflow is for locally working on new features in unstable branch and pushing them to the central repository.
-This workflow is only recommended for small features or where you are the only developer on a project.
-== Remote Feature Development ==
-This example workflow is for working on new features in a feature branch hosted on the central repository.
-This workflow is recommended for larger features or where there are many developers on a project.