Skip to content

[DO NOT MERGE] test to see if tests work #128

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.

Sign up for GitHub

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

Closed
cspath1 wants to merge 3 commits into from
Closed

[DO NOT MERGE] test to see if tests work #128

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d152728
Squashed commit of the following:
cspath1 Oct 29, 2025
3975422
Merge branch 'main' of github.com:launchdarkly/ld-openapi
cspath1 Oct 30, 2025
c64be39
test to see if tests are fixed
cspath1 Oct 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,3 +31,4 @@ That is the preferred way of doing releases, but the `make` targets can also be
Or, if you just want to look at the generated code locally, run `make targets_docker` which is equivalent to `make all` but uses a Docker container, so that the only tool you need to have installed locally is Docker. The output will appear in `./targets`. This is a convenient way to validate any local changes that relate to code generation. If you are also making changes that affect how the client code is packaged or published, it is better to use the slower but more comprehensive method of a Releaser dry run.

When running any `make` targets locally, set the environment variable `$LD_RELEASE_VERSION` to the version you are releasing, such as "6.0.0". It is set automatically when releases are run through Releaser.

Loading