meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
contribute [2024/12/30 13:05] – add maintainer steps wrongechocontribute [2025/01/09 16:50] (current) – mention $repo_branch in config.php wrongecho
Line 11: Line 11:
 **Steps to raise a PR** **Steps to raise a PR**
   - Fork the Project on GitHub   - Fork the Project on GitHub
-  - Clone the development branch: (''git clone --branch develop https://github.com/itflow-org/itflow.git'')+  - Clone the development branch: (''git clone //-//-branch develop https://github.com/itflow-org/itflow.git'')
   - Create your Feature Branch (''git checkout -b my-feature'')   - Create your Feature Branch (''git checkout -b my-feature'')
   - Commit your Changes (''git add something.txt && git commit -m 'Add some''')   - Commit your Changes (''git add something.txt && git commit -m 'Add some''')
Line 19: Line 19:
  
 **General Guidance** **General Guidance**
 +  * Don't forget to set your $repo_branch in config.php to 'develop'
   * Review the [[code_standards|code standards]] and the [[https://github.com/itflow-org/itflow/blob/master/CODE_OF_CONDUCT.md|code of conduct]]   * Review the [[code_standards|code standards]] and the [[https://github.com/itflow-org/itflow/blob/master/CODE_OF_CONDUCT.md|code of conduct]]
   * Discuss changes with the community first   * Discuss changes with the community first
Line 42: Line 43:
  
   - Ensure testing has been completed as much as possible   - Ensure testing has been completed as much as possible
-  - In develop, increment version.php in the YY.M.V format (e.g. 25.1 for the first release in Jan 2025, 25.1.2 for the second release of Jan 2025, and 25.6 for the first release in June 2025)+  - In develop, increment version.php in the YY.M.V format (e.g. 25.1 for the first release in Jan 2025, 25.1.1 for the second release of Jan 2025, and 25.6 for the first release in June 2025)
   - Look over the recent changes and write a short release summary   - Look over the recent changes and write a short release summary
   - Raise a PR to merge develop into master   - Raise a PR to merge develop into master
   - Test a final time on PR Review & ensure no other issues (Sonar, Linting, etc)   - Test a final time on PR Review & ensure no other issues (Sonar, Linting, etc)
   - Approve the PR & Merge   - Approve the PR & Merge