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

Merge upstream #1

Open
wants to merge 194 commits into
base: master
Choose a base branch
from
Open

Merge upstream #1

wants to merge 194 commits into from

Conversation

github-actions[bot]
Copy link

No description provided.

qoomon and others added 16 commits June 29, 2022 15:14
…"build.timestamp" (qoomon#207)

* Implement format placeholder `build.timestamp` based on `MavenSession#getStartTime`. It´s implemented in the same way as `commit.timestamp`

* Simple IT testcase

* Update documentation
… for each version component"

The intent of these changes is to open up an effective build number (via version label and "next by distance" based on the number of commits since last tag matching the version pattern). In our model we wish to use the label for this (hence the addition of version label as number) but it is entirely reasonable to treat the patch number as auto-incrementing with each commit the same way.
…ioning-extension into support-next-by-distance-and-label-as-number

� Conflicts:
�	README.md
�	src/main/java/me/qoomon/maven/gitversioning/GitVersioningModelProcessor.java
…R on the gradle plugin - small placeholder name changes
…alculate distance where matching tag isn't present (existing algorithm undercounts by 1 for this scenario. Added some tests to validate the "plus distance" placeholder behaviour.
…e-and-label-as-number

Support next by distance and label as number
@github-actions github-actions bot force-pushed the auto-upstream-merge branch 4 times, most recently from 616b931 to e6cfccf Compare August 23, 2022 03:35
@github-actions github-actions bot force-pushed the auto-upstream-merge branch 7 times, most recently from 47d1326 to bbf6db1 Compare August 30, 2022 03:45
@github-actions github-actions bot force-pushed the auto-upstream-merge branch 2 times, most recently from 49daf03 to 541ca1b Compare September 1, 2022 03:35
@github-actions github-actions bot force-pushed the auto-upstream-merge branch 8 times, most recently from 3620cf9 to bca151f Compare January 26, 2025 01:31
@github-actions github-actions bot force-pushed the auto-upstream-merge branch 7 times, most recently from f4f8a61 to 0765617 Compare February 2, 2025 01:31
@github-actions github-actions bot force-pushed the auto-upstream-merge branch 7 times, most recently from fa2719e to 48fd9ac Compare February 9, 2025 01:31
@github-actions github-actions bot force-pushed the auto-upstream-merge branch 6 times, most recently from 9cb53fe to f42a7df Compare February 15, 2025 01:31
@github-actions github-actions bot force-pushed the auto-upstream-merge branch from f42a7df to 15ffe48 Compare February 16, 2025 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

9 participants