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

fix(action): be more restrictive on the release branch format #8052

Merged
merged 2 commits into from
Dec 11, 2023

Conversation

gauthierpetetin
Copy link
Contributor

@gauthierpetetin gauthierpetetin commented Dec 8, 2023

Description

Every time a new release branch with format release/x.y.z is created, it triggers the creation of a bug report called: "vx.y.z Bug Report".
This works fine, but the problem we have is that it sometimes also creates bug reports in situations where we don’t want it, like when someone creates a branch called release/x.y.z-cherry-pick-swaps-content.

This fix adds more restrictions in the regex in order to prevent that.

Same PR for Extension

Related issues

Fixes: NA

Manual testing steps

Screenshots/Recordings

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • I've clearly explained what problem this PR is solving and how it is solved.
  • I've linked related issues
  • I've included manual testing steps
  • I've included screenshots/recordings if applicable
  • I’ve included tests if applicable
  • I’ve documented my code using JSDoc format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
  • I’ve properly set the pull request status:
    • In case it's not yet "ready for review", I've set it to "draft".
    • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Every time a new release branch with format release/x.y.z is created, it triggers the creation of a bug report called: vx.y.z Bug Report. This works fine, but the problem we have is that it sometimes also creates bug reports in situations where we don’t want it, like when someone creates a branch called release/x.y.z-cherry-pick-swaps-content. This commit adds more restrictions in the regex in order to prevent that.
Copy link
Contributor

github-actions bot commented Dec 8, 2023

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@metamaskbot metamaskbot added the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label Dec 8, 2023
Copy link
Contributor

@NicolasMassart NicolasMassart 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 to me.

Copy link
Contributor

@MarioAslau MarioAslau 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!

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9cb095c) 37.14% compared to head (037bfcd) 37.14%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8052   +/-   ##
=======================================
  Coverage   37.14%   37.14%           
=======================================
  Files        1139     1139           
  Lines       29196    29196           
  Branches     2746     2746           
=======================================
  Hits        10846    10846           
  Misses      17724    17724           
  Partials      626      626           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@gauthierpetetin gauthierpetetin merged commit 2c877b3 into main Dec 11, 2023
26 checks passed
@gauthierpetetin gauthierpetetin deleted the fix/bug-report-creation-regex branch December 11, 2023 08:25
@github-actions github-actions bot removed the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label Dec 11, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Dec 11, 2023
@metamaskbot metamaskbot added the release-7.15.0 Issue or pull request that will be included in release 7.15.0 label Dec 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-7.15.0 Issue or pull request that will be included in release 7.15.0 team-mobile-platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants