If you have a local clone of the repository that **predates Feb. 19th, 2025, you must absolutely make a new clone**.
If you have a local clone of the repository that **predates Feb. 19th, 2025, you must absolutely make a new clone**.
...
@@ -23,7 +15,7 @@ The procedure depends on if you have local unpushed changes.
...
@@ -23,7 +15,7 @@ The procedure depends on if you have local unpushed changes.
All contributions are welcome. To start coding :
All contributions are welcome. To start coding :
- read this developer guide **completely** for essential information and practices to follow
- read this developer guide **completely** for essential information and practices to follow
- either check the [issues](https://gitlab.uliege.be/deal-public/pase/-/issues) or get in touch with the team (see [Contact](contact) page) to join the collaboration
- either check the [issues](https://gitlab.uliege.be/deal-public/pase/-/issues) or get in touch with the team (see [Contact](contact) page) to join the collaboration
- clone or fork the repository
- clone or fork the repository (contributions via the forking workflow ([see e.g. Gitlab Docs about Forks](https://docs.gitlab.com/user/project/repository/forking_workflow/)) are accepted, provided all push rules are followed ; continue reading the guide for more details).
- use an existing branch or create one according to the [branching workflow](#branching-workflow)
- use an existing branch or create one according to the [branching workflow](#branching-workflow)
- edit or add to the code, making sure to follow the [Push rules](#push-rules) and other guidelines from this wiki !
- edit or add to the code, making sure to follow the [Push rules](#push-rules) and other guidelines from this wiki !
