Changes between Version 96 and Version 97 of HowToGit


Ignore:
Timestamp:
08/23/21 19:30:40 (3 years ago)
Author:
wenzeslaus
Comment:

General update and master to main

Legend:

Unmodified
Added
Removed
Modified

  • HowToGit

    v96 v97  
    1010Below we discuss more advanced and specific workflows.
    1111
    12 If you are long-term GRASS GIS contributor, please note that the development workflow changed significanly after [https://trac.osgeo.org/grass/wiki/GitMigration#ImplementationofmigrationfromOSGeoSVNandtractoGitHub migration from Subversion to Git] (!GitHub).
     12If you are long-term GRASS GIS contributor, please note that the development workflow changed significantly after [https://trac.osgeo.org/grass/wiki/GitMigration#ImplementationofmigrationfromOSGeoSVNandtractoGitHub migration from Subversion to Git] (!GitHub).
    1313
    1414Important changes:
    15  * direct committing to "master" (former "trunk") is a no-go and highly discouraged
    16  * hence: you will create a feature branch and open a pull request for a change
    17    * Rationale: pull requests are the perfect platform to discuss/improve changes before merging.
    18    * also applies to core developers (to be discussed)
    19 
    20 Workflow
    21  * fork the GRASS GIS repository, and create feature branch(es) with the changes, and suggest your changes as pull requests.
     15 * Direct committing to "main" (former "trunk" and "master") is not allowed.
     16 * Hence, you will create a feature branch and open a pull request for a change.
     17   * Rationale: Pull requests are the perfect platform to discuss, improve, and check changes before merging.
     18   * This applies to both contributors and core developers.
     19
     20Workflow:
     21 * Fork the GRASS GIS repository, create feature branch(es) with the changes, and suggest your changes using pull requests.
    2222
    2323=== Workflow for GRASS GIS git repositories ===