II.
Methodology JSON
Structured · livemethodology:GitFlow
GitFlow json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "methodology:GitFlow",
"_kind": "Methodology",
"_file": "domain/methodologies/methodologies-expanded.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "GitFlow",
"description": "A branching model for Git that defines a strict branching structure with\ndedicated branches for features, releases, hotfixes, and development. Uses\nlong-lived develop and main branches with merge-based integration. Well-suited\nfor projects with scheduled release cycles but criticized for complexity\nin continuous delivery environments.\n",
"methodologyKind": "engineering-practice",
"origin": "Vincent Driessen",
"yearIntroduced": "2010"
},
"outgoingEdges": [
{
"from": "methodology:GitFlow",
"to": "domain:software-engineering",
"kind": "applies_to"
},
{
"from": "methodology:GitFlow",
"to": "domain:devops",
"kind": "applies_to"
},
{
"from": "methodology:GitFlow",
"to": "platform:krate",
"kind": "applies_to",
"attributes": {
"notes": "Krate branch protection supports GitFlow branching models"
}
}
],
"incomingEdges": []
}