Skip to content

Conversation

ctinp
Copy link

@ctinp ctinp commented Aug 19, 2025

Please ensure your pull request adheres to the following guidelines:

  • make sure to link the related issues in this description. Or if there's no issue created, make sure you
    describe here the problem you're solving.
  • when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

If the PR is changing the API specification:

  • make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready
    yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
  • make sure you add at least one example of the request and response.

If the PR is changing the API implementation or an entity exposed through the API:

  • make sure you update the API specification and the examples to reflect the changes.

If the PR is introducing a new audit type:

  • make sure you update the API specification with the type, schema of the audit result and an example

Related Issues

Thanks for contributing!

@ctinp ctinp force-pushed the cdn-logs-bucket-api branch from 73fc10d to 2b264b7 Compare August 19, 2025 14:43
Copy link

This PR will trigger a minor release when merged.

@ctinp ctinp force-pushed the cdn-logs-bucket-api branch 11 times, most recently from e0e9ecd to 3b42e14 Compare August 26, 2025 12:18
@ctinp ctinp force-pushed the cdn-logs-bucket-api branch from 3b42e14 to aa0f253 Compare August 26, 2025 12:22
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.

1 participant