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

WPB-5017: Adding a test config file to the PR guidelines. #3624

Merged
merged 4 commits into from
Oct 16, 2023

Conversation

lepsa
Copy link
Contributor

@lepsa lepsa commented Sep 29, 2023

Changes

Adding a testing config file to the PR guidelines.

Checklist

  • [:heavy_check_mark:] Add a new entry in an appropriate subdirectory of changelog.d
  • [:heavy_check_mark:] Read and follow the PR guidelines

@@ -81,7 +81,7 @@ Add to `charts/nginz/values.yaml`, under the `galley` section:
If a PR adds new configuration options for say brig, the following files need to be edited:

* [ ] The parser under `services/brig/src/Brig/Options.hs`
* [ ] The integration test config: `services/brig/brig.integration.yaml`
* [ ] The integration test config: `services/brig/brig.integration.yaml` and `charts/cargohold/templates/tests/configmap.yaml`
Copy link
Contributor

Choose a reason for hiding this comment

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

ah, wait, this was already documented, but you have to read the context carefully. this list is an example for the context where you made changes to brig. for cargohold, most items in this list will change.

do you have a suggestion how to make this more clear? maybe introduce variables $Service and $service to use in the list instead of brig?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Variables would work, I think. I'll sit with this a bit and see what I can come up with.

@lepsa lepsa changed the title Hotfix: Adding a test config file to the PR guidelines. WPB-5017: Adding a test config file to the PR guidelines. Oct 11, 2023
Copy link
Contributor

@pcapriotti pcapriotti left a comment

Choose a reason for hiding this comment

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

This is fine, but you could also add the item to the previous list, and simply use brig instead of $SERVICE, continuing the example.

@fisx fisx merged commit c37d94f into wireapp:develop Oct 16, 2023
3 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.

3 participants