Skip to content

[OPAL-9463] Adding PR guidelines to the onprem repo#7

Merged
audrei-opal merged 2 commits into
mainfrom
audrei-vs-repo-guidelines
Feb 22, 2024
Merged

[OPAL-9463] Adding PR guidelines to the onprem repo#7
audrei-opal merged 2 commits into
mainfrom
audrei-vs-repo-guidelines

Conversation

@audrei-opal

Copy link
Copy Markdown
Contributor

Description

Adding some protections to the onprem repo ✨

Release Notes Description

N/A

Risk

What is the level of risk to the product with this change? And why? (Low, High)

Low

If "High", what monitoring do we have in place to let us know if something goes wrong?

Testing

N/A

Checklist

@audrei-opal audrei-opal changed the title Adding PR guidelines to the onprem repo [OPAL-9463] Adding PR guidelines to the onprem repo Feb 22, 2024
@linear

linear Bot commented Feb 22, 2024

Copy link
Copy Markdown

@audrei-opal
audrei-opal requested a review from a team February 22, 2024 19:08
evan-opal
evan-opal previously approved these changes Feb 22, 2024
Comment thread .github/pull_request_template.md Outdated

> What is the level of risk to the product with this change? And why? (Low, High)

<!-- High areas of risk would include infrastructure changes, including DB migrations, changing how users get access to resources, potential side effects for no-prem customers, breaking changes to the public API, etc -->

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

nit: no-prem should be on-prem

@audrei-opal

Copy link
Copy Markdown
Contributor Author

@evan-opal would you mind taking another look? I turned on dismissing approvals if changes are pushed 😬

@evan-opal evan-opal left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

lgtm. I assume that even though this repo is public, we're still only expecting Opal engineers to create PRs here.

@audrei-opal

Copy link
Copy Markdown
Contributor Author

lgtm. I assume that even though this repo is public, we're still only expecting Opal engineers to create PRs here.

@evan-opal That's my current understanding

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants