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 Management documentation #229
Conversation
AureRita
commented
Oct 17, 2023
Questions | Answers |
---|---|
Description | Create the documentation to "how to test manually a PR" |
Fixed ticket | NA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing launching of automated test part, + some things to fix
content/project-organization/quality-council/processes/pr-management.md
Outdated
Show resolved
Hide resolved
content/project-organization/quality-council/processes/pr-management.md
Outdated
Show resolved
Hide resolved
To do this, go to your terminal and execute the commands below: | ||
|
||
|
||
ℹ️ For your information, I recommend that you put it in the *Computer/var/www/html* folder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For Mac it's the same or not? Maybe it would be useful to precise specify which environment is targeted by this documentation.
|
||
We can see that in **violet** we've put the "**Branch "** we're interested in and in **brown** the name of our file, which can be modified as we wish. | ||
|
||
Still with this **Branch**, I advise you to launch the automated Tests. To do this, I suggest you look at the end of this chapter dedicated to it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still with this **Branch**, I advise you to launch the automated Tests. To do this, I suggest you look at the end of this chapter dedicated to it. | |
Still with this **Branch**, we advise you to launch the automated Tests. To do this, we suggest you to look at the end of the chapter dedicated to it. |
|
||
We can see that in **violet** we've put the "**Branch "** we're interested in and in **brown** the name of our file, which can be modified as we wish. | ||
|
||
Still with this **Branch**, I advise you to launch the automated Tests. To do this, I suggest you look at the end of this chapter dedicated to it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't find the chapter dedicated to the launch of automated tests, is it me or it's missing?
![img.png](images/readme16.png) | ||
|
||
- The PR is not valid. In this case, indicate that it doesn't work, put a video showing that it doesn't work and put the link to the automated tests (to prove that it brings issues). | ||
In your comment, you'll need to select the Comment option before submitting the review. The Request changes option doesn't work properly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this part still up to date?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't know, I continue to apply this method because if we don't, we have to accept the PR at the end, another QA can't approve it
content/project-organization/quality-council/processes/pr-management.md
Outdated
Show resolved
Hide resolved
content/project-organization/quality-council/processes/pr-management.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Robin-Fischer-PS <55688534+Robin-Fischer-PS@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now :)