Skip to content

update the PR template to clarify the requirement on tools provider check #104

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
Apr 14, 2022

Conversation

yangcao77
Copy link
Contributor

@yangcao77 yangcao77 commented Mar 31, 2022

Signed-off-by: Stephanie [email protected]

What does this PR do?:

Summarize the changes. Are any stacks or samples added or updated?
update the PR template to include an additional check in PR acceptance criteria to clarify the requirement to check on tools

Which issue(s) this PR fixes:

Link to github issue(s)
Fixes devfile/api#814

PR acceptance criteria:

  • Contributing guide
    Have you read the devfile registry contributing guide and followed its instructions?
  • Test automation
    Does this repository's tests pass with your changes?
  • Documentation
    Does any documentation need to be updated with your changes?

How to test changes / Special notes to the reviewer:

Signed-off-by: Stephanie <[email protected]>
@@ -12,6 +12,8 @@ _Have you read the [devfile registry contributing guide](https://github.com/devf
_Does this repository's tests pass with your changes?_
- [ ] Documentation
_Does any documentation need to be updated with your changes?_
- [ ] Check Tools Provider
_Does this change impact existing tools, i.e. Odo, Che, Console? If it does, have you tested the change with those tools?_
Copy link
Contributor

@elsony elsony Mar 31, 2022

Choose a reason for hiding this comment

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

I wonder how the developer can answer this if they are not familiar with the impact of all of the tools. We may want to provide a link to provide more info on that so that the developer knows how to answer this question properly.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

talked with Tomas and Mario, they both suggest any change to registry need to be verified with tools to ensure it won't break tools. Reword the sentence to clarify the requirement to test with tools. Also updated the contributing.md to include instruction on how to test with existing tools providers.

@yangcao77
Copy link
Contributor Author

/retest

Copy link
Contributor

@elsony elsony left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Looks good to me label Apr 14, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 14, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elsony, yangcao77

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@yangcao77 yangcao77 merged commit c1763de into devfile:main Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Looks good to me
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update PR template to clarify the requirement on tools provider check
2 participants