mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-04-29 19:45:01 +02:00
Code Issues Wiki Activity

Fixed links in md files

Browse source 
Signed-off-by: Torbjörn Svensson <torbjorn.svensson@st.com>
This commit is contained in:
Torbjörn Svensson 2022-08-16 15:22:34 +02:00 • committed by Torbjorn-Svensson
parent 5aee96dfb4
commit 2089c1d314
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
GitHubMigration.md
View file

@ -20,9 +20,9 @@ Please see the GitHub issues on the migration for current status and things left
- Note that one of the drawbacks of decentralized GitHub issues is that each project has its own set of "numbers".
- Therefore when referencing an issues from outside of the current repo, prefixing it with the project name is the proper way to do it. e.g. `Organization_name/Repository#Issue` - see [GitHub help](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls) for more details.
- Bug reports are not necessary on Pull Requests. Issues and Pull Requests in GitHub share a numbering system and the metadata that can be applied to them is the same. So unlike the Bugzilla/Gerrit flow it is no longer necessary to create issues for each PR. See (contribution guide's Creating Pull Requests section)[CONTRIBUTING.md#Creating-Pull-Requests] for current policy
- Bug reports are not necessary on Pull Requests. Issues and Pull Requests in GitHub share a numbering system and the metadata that can be applied to them is the same. So unlike the Bugzilla/Gerrit flow it is no longer necessary to create issues for each PR. See [contribution guide's Creating Pull Requests section](CONTRIBUTING.md#Creating-Pull-Requests) for current policy
- GitHub Pull Requests replace Gerrit. See (contribution guide's Creating Pull Requests section)[CONTRIBUTING.md#Creating-Pull-Requests] for step-by-step on creating PRs, and the (Merge Pull Request)[CONTRIBUTING.md#Merge-Pull-Request] section for how to review and merge issues
- GitHub Pull Requests replace Gerrit. See [contribution guide's Creating Pull Requests section](CONTRIBUTING.md#Creating-Pull-Requests) for step-by-step on creating PRs, and the [Merge Pull Request](CONTRIBUTING.md#Merge-Pull-Request) section for how to review and merge issues
- Where possible we borrow for the Eclipse Platform project on process. The Eclipse Platform have a [recommended workflow](https://github.com/eclipse-platform/.github/blob/main/CONTRIBUTING.md#recommended-workflow) that is evolving that Eclipse CDT should use.
- CDT's contribution + pull request process are documented in [CONTRIBUTING.md](CONTRIBUTING.md)

4
POLICY.md
View file

@ -15,7 +15,7 @@ Externalize strings (excluding exception arguments, tests and special identifier
All CDT plugins override default compiler error/warning and use project specific errors/warnings. This enforced by the [build process](https://github.com/eclipse-cdt/cdt-infra/tree/master/jenkins/pipelines/cdt/verify#cdt-verify-code-cleanliness).
All committers and contributors submitting patches should enable [http://wiki.eclipse.org/PDE/API_Tools/User_Guide#API_Tooling_Setup API tooling] by setting target baseline platform. Do not commit code with API errors.
All committers and contributors submitting patches should enable [API tooling](http://wiki.eclipse.org/PDE/API_Tools/User_Guide#API_Tooling_Setup) by setting target baseline platform. Do not commit code with API errors.
*Patches with errors listed above including API errors will not be accepted without corrections.*
@ -86,7 +86,7 @@ Once this is done, a full build will be triggered. After that, any changes that
4. Click "Refresh" to update the contents of the target.
5. Click "Finish", then "OK" in the next dialog.
(In the future, refreshing manually might not be required, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=479055 bug 479055])
(In the future, refreshing manually might not be required, see [bug 479055](https://bugs.eclipse.org/bugs/show_bug.cgi?id=479055))
## Javadoc