Skip to content

Simplify pull request template headers and instructions #11920

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.

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
merged 3 commits into from
Dec 3, 2019
Merged

Conversation

adbridge
Copy link
Contributor

@adbridge adbridge commented Nov 21, 2019

Template updated here to show what the new one will look like:

Summary of changes

There is confusion with having sub headings below Description and duplication of fields between
main description and release notes section.

This PR removes the Description header completely and promotes
sub headings to full headings. It also removes the release notes section completely and promotes the implication and migration sections.

Some of the notes under each heading have also been updated to
provide better clarity.

Impact of changes

Mbed-release script will require updates to allow for new format.

Migration actions required

Documentation

https://os.mbed.com/docs/mbed-os/latest/contributing/workflow.html will require updates


Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[ ] Feature update (New feature / Functionality change / New API)
[ ] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[x] No Tests required for this change (E.g docs only update)
[ ] Covered by existing mbed-os tests (Greentea or Unittest)
[ ] Tests / results supplied as part of this PR

Reviewers


There is confusion with having sub headings below Description.
This commit removes teh Description header completely and promotes
sub headings to full headings.

Some of the notes under each heading have also been updated to
provide better clarity.
@adbridge adbridge requested review from bulislaw and 0xc0170 November 21, 2019 16:22
@adbridge adbridge changed the title Simplify headers and instructions Simplify pull request template headers and instructions Nov 21, 2019
@ciarmcom
Copy link
Member

@adbridge, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

@ciarmcom ciarmcom requested a review from a team November 21, 2019 18:00
Feedback has shown that having similar fields in the release notes
section to the main headings is confusing. This PR simplifies the
sections and removes the release notes section completely.

Changes will be required to the release scripts and the docs to
reflect these changes.
Why the change is needed (if this is fixing a reported issue please summarize what
the issue is and add the reference. E.g. Fixes #17119).

Any implications for users taking this change.
Copy link
Member

@bulislaw bulislaw Nov 22, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's repeated in the next point

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed


-->

### Impact of changes <!-- Optional -->
Copy link
Contributor

@0xc0170 0xc0170 Nov 22, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When looking at rendered text, this is the same as summary of changes ( using ###) , would it be better as this is option to be done with one less (####) ? As these two (migration, impact) are optional most of the time.

Wouldn't this be the same in the release notes? Summary of changes as the main text, subsections in there are migration action and impact?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could do that yes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@adbridge adbridge added the release-version: 6.0.0-alpha-1 First pre-release version of 6.0.0 label Nov 22, 2019
@0xc0170
Copy link
Contributor

0xc0170 commented Dec 3, 2019

@adbridge As 5.15 branch was created, can this land now?

CI started

@adbridge
Copy link
Contributor Author

adbridge commented Dec 3, 2019

@adbridge As 5.15 branch was created, can this land now?

CI started

Should be ok yes

@0xc0170 0xc0170 removed the needs: CI label Dec 3, 2019
@0xc0170 0xc0170 merged commit 888dfff into master Dec 3, 2019
@0xc0170 0xc0170 deleted the pr_template branch October 7, 2021 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-version: 6.0.0-alpha-1 First pre-release version of 6.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants