Skip to content
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

PR Cop 2.0 #5815

Merged
merged 5 commits into from
Dec 14, 2023
Merged

PR Cop 2.0 #5815

merged 5 commits into from
Dec 14, 2023

Conversation

unlikelyzero
Copy link
Collaborator

@unlikelyzero unlikelyzero commented Sep 28, 2022

Contributes towards /issues/5755

Describe your changes:

  • Enforces a type label
  • Enforces a milestone

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Is this change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.

Author Checklist

  • Changes address original issue?
  • Tests included and/or updated with changes?
  • Command line build passes?
  • Has this been smoke tested?
  • Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

  • Changes appear to address issue?
  • Changes appear not to be breaking changes?
  • Appropriate unit tests included?
  • Code style and in-line documentation are appropriate?
  • Commit messages meet standards?
  • Has associated issue been labelled unverified? (only applicable if this PR closes the issue)
  • Has associated issue been labelled bug? (only applicable if this PR is for a bug fix)

@unlikelyzero unlikelyzero added this to the Target:2.1.1 milestone Sep 28, 2022
@unlikelyzero unlikelyzero added the type:maintenance tests, chores, or project maintenance label Sep 28, 2022
@codecov
Copy link

codecov bot commented Sep 28, 2022

Codecov Report

Merging #5815 (86d5be5) into master (97bffc5) will decrease coverage by 0.23%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5815      +/-   ##
==========================================
- Coverage   55.90%   55.67%   -0.23%     
==========================================
  Files         655      655              
  Lines       26316    26316              
  Branches     2543     2543              
==========================================
- Hits        14712    14652      -60     
- Misses      10892    10956      +64     
+ Partials      712      708       -4     
Flag Coverage Δ *Carryforward flag
e2e-full 41.86% <ø> (ø) Carriedforward from 3f2dbdf
e2e-stable 58.49% <ø> (+0.08%) ⬆️
unit 48.76% <ø> (-0.40%) ⬇️

*This pull request uses carry forward flags. Click here to find out more.

see 16 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 97bffc5...86d5be5. Read the comment docs.

@akhenry akhenry requested a review from ozyx October 3, 2022 20:51
Copy link
Contributor

@ozyx ozyx left a comment

Choose a reason for hiding this comment

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

Looks good!
Couple questions:

  • With this change, every PR must have either a milestone or the "no milestone" label?
  • What does the developer see if a PR fails merge check due to missing milestone or type: label? Is it clear enough?

* [ ] Have you followed the guidelines in our [Contributing document](https://github.com/nasa/openmct/blob/master/CONTRIBUTING.md)?
* [ ] Have you associated this PR with a `type:` label?
* [ ] Have you associated a milestone with this PR?
* [ ] Testing instructions included in associated issue OR is this a dependency/testcase change?
### Author Checklist
Copy link
Contributor

Choose a reason for hiding this comment

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

can we just get a space before this to be consistent with the other headers?

* [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/nasa/openmct/pulls) for the same update/change?
* [ ] Is this change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.

### Contribution Checklist
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we note that both authors and reviewers should verify this section?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah I'm confused about who the intended audience is here. How does it differ from the author checklist?

Copy link
Contributor

@jvigliotta jvigliotta left a comment

Choose a reason for hiding this comment

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

Looks good! Just a suggestion and a formatting fix.

.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
* [ ] Have you checked to ensure there aren't other open [Pull Requests](https://github.com/nasa/openmct/pulls) for the same update/change?
* [ ] Is this change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.

### Contribution Checklist
Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah I'm confused about who the intended audience is here. How does it differ from the author checklist?

@unlikelyzero unlikelyzero modified the milestones: Target:2.1.2, 2.1.3 Nov 10, 2022
Copy link
Contributor

@charlesh88 charlesh88 left a comment

Choose a reason for hiding this comment

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

  • How does one know how to set a milestone? Can the system not require a milestone, but add "No milestone" if one isn't entered?
  • Similar question about type labels. Like the idea of automatically pulling from an issue, but what if the user hasn't tied an issue to the PR?

@ozyx ozyx modified the milestones: Target:2.1.4, Target:2.1.5 Dec 6, 2022
Copy link
Contributor

@ozyx ozyx left a comment

Choose a reason for hiding this comment

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

I have some outstanding questions, didn't mark as "request changes" before, so marking that now so it's shown as reviewed

@akhenry
Copy link
Contributor

akhenry commented Jan 9, 2023

@shefalijoshi to review

@jvigliotta
Copy link
Contributor

@unlikelyzero were you able to address my comments? I'm not seeing it

.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
.github/PULL_REQUEST_TEMPLATE.md Outdated Show resolved Hide resolved
.github/PULL_REQUEST_TEMPLATE.md Show resolved Hide resolved
@unlikelyzero unlikelyzero removed this from the Target:2.1.6 milestone Jan 20, 2023
@unlikelyzero unlikelyzero added this to the Target:3.3.0 milestone Dec 14, 2023
Copy link

deploysentinel bot commented Dec 14, 2023

Current Playwright Test Results Summary

✅ 165 Passing - ⚠️ 4 Flaky

Run may still be in progress, this comment will be updated as current testing workflow or job completes...

(Last updated on 12/14/2023 03:09:01pm UTC)

Run Details

Running Job e2e-stable on CircleCI

Commit: 86d5be5

Started: 12/14/2023 03:01:24pm UTC

⚠️ Flakes

📄   functional/plugins/telemetryTable/telemetryTable.e2e.spec.js • 1 Flake

Test Case Results

Test Case Last 7 days Failures Last 7 days Flakes
Telemetry Table unpauses and filters data when paused by button and user changes bounds
Retry 2Retry 1Initial Attempt
0% (0) 0 / 39 runs
failed over last 7 days
17.95% (7) 7 / 39 runs
flaked over last 7 days

📄   functional/plugins/notebook/restrictedNotebook.e2e.spec.js • 1 Flake

Test Case Results

Test Case Last 7 days Failures Last 7 days Flakes
Restricted Notebook with a page locked and with an embed @addinit Disallows embeds to be deleted if page locked @addinit
Retry 1Initial Attempt
0% (0) 0 / 39 runs
failed over last 7 days
41.03% (16) 16 / 39 runs
flaked over last 7 days

📄   functional/plugins/imagery/exampleImagery.e2e.spec.js • 1 Flake

Test Case Results

Test Case Last 7 days Failures Last 7 days Flakes
Example Imagery Object Can use Mouse Wheel to zoom in and out of latest image
Retry 1Initial Attempt
0% (0) 0 / 39 runs
failed over last 7 days
15.38% (6) 6 / 39 runs
flaked over last 7 days

📄   functional/plugins/notebook/notebookSnapshots.e2e.spec.js • 1 Flake

Test Case Results

Test Case Last 7 days Failures Last 7 days Flakes
Snapshot image tests Can drop an image onto a notebook and create a new entry
Retry 1Initial Attempt
0% (0) 0 / 38 runs
failed over last 7 days
57.89% (22) 22 / 38 runs
flaked over last 7 days

View Detailed Build Results


@unlikelyzero
Copy link
Collaborator Author

Yeah I'm confused about who the intended audience is here. How does it differ from the author checklist?
@akhenry it meant that ownership was shared by everyone and not something that the author or reviewer had to follow explicitly. The intent was for the release manager to set this if not already set

@@ -14,8 +14,10 @@ Closes <!--- Insert Issue Number(s) this PR addresses. Start by typing # will op

* [ ] Changes address original issue?
* [ ] Tests included and/or updated with changes?
* [ ] Command line build passes?
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

no longer necessary with our ci

Copy link
Contributor

@jvigliotta jvigliotta left a comment

Choose a reason for hiding this comment

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

LGTM!

@unlikelyzero unlikelyzero merged commit 4075a31 into master Dec 14, 2023
14 of 15 checks passed
@unlikelyzero unlikelyzero deleted the pr-cop-two branch December 14, 2023 18:55
@unlikelyzero unlikelyzero modified the milestones: Target:3.3.0, Target:4.0.0 Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:maintenance tests, chores, or project maintenance
Projects
None yet
Development

Successfully merging this pull request may close these issues.