Skip to content

Add info on needing tags for CI features test #2623

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

Merged
yuandrew merged 2 commits into from
Aug 13, 2025
Merged

Add info on needing tags for CI features test #2623

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6fba2d
Add info on features test issue for CI
yuandrew Aug 8, 2025
dca8ac5
Merge branch 'master' into features-ci-tags
yuandrew Aug 13, 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
11 changes: 11 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,17 @@ Overcommit adds some requirements to your commit messages. We follow the
[Chris Beams](http://chris.beams.io/posts/git-commit/) guide to writing git
commit messages. Read it, follow it, learn it, love it.

## Running features tests in CI

For each PR we run the java tests from the [features repo](https://github.com/temporalio/features/). This requires
your branch to have tags. Without tags, the features tests in CI will fail with a message like
```
> Configure project :sdk-java
fatal: No names found, cannot describe anything.
```
This can be done resolved by running `git fetch --tags` on your branch. Note, make sure your fork has tags copied from
the main repo.

## Test and Build

Testing and building `sdk-java` requires running temporal docker locally, execute:
Expand Down
Loading