Skip to content

Remove the instruction to start a PR title with the PWG name #278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ddobrigk merged 1 commit into from
Oct 31, 2024
Merged

Remove the instruction to start a PR title with the PWG name #278

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/advanced-specifics/pwghf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,7 +279,5 @@ Example:

- Update your branch and test it before creating a PR.
- Give your PR a short meaningful title.
- Add the “PWGHF: ” prefix in the title of your PR. (It helps to search for PWGHF-related PRs in the commit history of the main branch.)
- Note: If your PR has only one commit, add the prefix also in the commit title (because that is the title that will appear in the history after merging, unless the person merging the PR changes it by hand).
- Give further useful details about your changes in the PR description.
- Add links to all related PRs (e.g. O2Physics, O2, AliPhysics, Run3Analysisvalidation) in the PR description.
1 change: 0 additions & 1 deletion docs/gettingstarted/contributingtocode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,6 @@ __Give your pull request a short and meaningful title.__

- The title should be informative enough to give an idea of _what_ was changed and _where_.
- Further details (e.g. _why_ this change is needed or related links) can be provided in the description below the title.
- It is useful to put the PWG name at the beginning of the PR title to specify the scope of the changes, which makes it easier to filter PRs related to the PWG in the PR history and also in the commit history of the main branch.
- Examples of too vague titles: "Test", "Fix bug", "Add new parameter", "Update cuts", "Improve code".

### Automatic checks
Expand Down
Loading