-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ci: regenerated with OpenAPI Doc , Speakeasy CLI 1.396.9
- Loading branch information
1 parent
b190383
commit ce73a7b
Showing
459 changed files
with
20,147 additions
and
5,132 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3,795 changes: 3,795 additions & 0 deletions
3,795
previous-versions/sync-for-commerce-version-1/.speakeasy/gen.lock
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
26 changes: 26 additions & 0 deletions
26
previous-versions/sync-for-commerce-version-1/CONTRIBUTING.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Contributing to This Repository | ||
|
||
Thank you for your interest in contributing to this repository. Please note that this repository contains generated code. As such, we do not accept direct changes or pull requests. Instead, we encourage you to follow the guidelines below to report issues and suggest improvements. | ||
|
||
## How to Report Issues | ||
|
||
If you encounter any bugs or have suggestions for improvements, please open an issue on GitHub. When reporting an issue, please provide as much detail as possible to help us reproduce the problem. This includes: | ||
|
||
- A clear and descriptive title | ||
- Steps to reproduce the issue | ||
- Expected and actual behavior | ||
- Any relevant logs, screenshots, or error messages | ||
- Information about your environment (e.g., operating system, software versions) | ||
- For example can be collected using the `npx envinfo` command from your terminal if you have Node.js installed | ||
|
||
## Issue Triage and Upstream Fixes | ||
|
||
We will review and triage issues as quickly as possible. Our goal is to address bugs and incorporate improvements in the upstream source code. Fixes will be included in the next generation of the generated code. | ||
|
||
## Contact | ||
|
||
If you have any questions or need further assistance, please feel free to reach out by opening an issue. | ||
|
||
Thank you for your understanding and cooperation! | ||
|
||
The Maintainers |
Oops, something went wrong.