Skip to content

Conversation

baileympearson
Copy link
Contributor

Description

What is changing?

Adds a check that confirms that documentation generation and the release process is only run on a clone of the main repo and not a fork.

Is there new documentation needed for these changes?

No.

Copy link
Contributor

@dariakp dariakp left a comment

Choose a reason for hiding this comment

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

LGTM, but could you include a screenshot of what this looks like right now from your fork in both cases (the release with a --dry-run), and then also in main? Just as a sanity check?

@baileympearson
Copy link
Contributor Author

Example num run release from main:
Screen Shot 2022-11-16 at 10 14 48 AM

Example num run release from my fork:
Screen Shot 2022-11-16 at 10 11 36 AM

@baileympearson
Copy link
Contributor Author

evergreen retry

@dariakp dariakp added the Team Review Needs review from team label Nov 21, 2022
@baileympearson baileympearson merged commit c4c560c into mongodb:main Nov 21, 2022
@baileympearson baileympearson deleted the NODE-4824 branch November 21, 2022 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Team Review Needs review from team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants