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

docs: updated the developer guide #5347

Merged
merged 3 commits into from
Feb 25, 2025
Merged

Conversation

Anu-Ra-g
Copy link
Contributor

What type of PR is this?
Documentation changes

What this PR does / why we need it:
This contains the steps to perform when raising a PR in the repository.

Which issue(s) this PR fixes:
Fixes #5346

Release Notes: No

@Anu-Ra-g Anu-Ra-g requested a review from a team as a code owner February 25, 2025 05:57
Copy link

codecov bot commented Feb 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.97%. Comparing base (1b64996) to head (002174f).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5347      +/-   ##
==========================================
+ Coverage   64.95%   64.97%   +0.02%     
==========================================
  Files         213      213              
  Lines       33474    33474              
==========================================
+ Hits        21742    21750       +8     
+ Misses      10402    10396       -6     
+ Partials     1330     1328       -2     

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

zirain
zirain previously approved these changes Feb 25, 2025
### Raising a PR

* Run `make generate` and push the generated files along with your commit, if your PR contains any API changes (`/api`) or you've added some unit tests or you've updated the modules used in the project.

Copy link
Contributor

Choose a reason for hiding this comment

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

can we also add a line here on make testdata - which generates output testdata

Copy link
Contributor Author

@Anu-Ra-g Anu-Ra-g Feb 25, 2025

Choose a reason for hiding this comment

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

It's already present in the testing section. Should I add it here also?
image

Copy link
Contributor

Choose a reason for hiding this comment

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

cool thanks

Signed-off-by: Anu-Ra-g <[email protected]>
@Anu-Ra-g
Copy link
Contributor Author

Anu-Ra-g commented Feb 25, 2025

@arkodg Can you please also review this PR #5328?

@arkodg
Copy link
Contributor

arkodg commented Feb 25, 2025

can you also add a note in https://github.com/envoyproxy/gateway/blob/main/.github/PULL_REQUEST_TEMPLATE.md that shows up as a comment, mentioning to go through https://gateway.envoyproxy.io/contributions/develop/#raising-a-pr

@Anu-Ra-g
Copy link
Contributor Author

@arkodg I've made the changes

Copy link
Contributor

@arkodg arkodg left a comment

Choose a reason for hiding this comment

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

thanks !

@arkodg arkodg merged commit 946d5c2 into envoyproxy:main Feb 25, 2025
28 checks passed
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.

docs: Improve common contributor/developer workflows
3 participants