Skip to content

Conversation

puehringer
Copy link
Contributor

Closes list issues numbers here

Developer Checklist (Definition of Done)

Issue

  • All acceptance criteria from the issue are met
  • Tested in latest Chrome/Firefox

UI/UX/Vis

  • Requires UI/UX/Vis review
    • Reviewer(s) are notified (tag assignees)
    • Review has occurred (link to notes)
    • Feedback is included in this PR
    • Reviewer(s) approve of concept and design

Code

  • Branch is up-to-date with the branch to be merged with, i.e., develop
  • Code is cleaned up and formatted
  • Unit tests are written (frontend/backend if applicable)
  • Integration tests are written (if applicable)

PR

  • Descriptive title for this pull request is provided (will be used for release notes later)
  • Reviewer and assignees are defined
  • Add type label (e.g., bug, feature) to this pull request
  • Add release label (e.g., release: minor) to this PR following semver
  • The PR is connected to the corresponding issue (via Closes #...)
  • Summary of changes is written

Summary of changes

Screenshots

Additional notes for the reviewer(s)

Thanks for creating this pull request 🤗

@puehringer puehringer requested a review from a team as a code owner September 20, 2025 20:54
@puehringer puehringer changed the title feat: make GIT_BRANCH and GIT_COMMIT available as env variables feat: make GIT_BRANCH and GIT_COMMIT_HASH available as env variables Sep 20, 2025
@puehringer puehringer merged commit baad6fc into develop Oct 8, 2025
1 check passed
@puehringer puehringer deleted the mp/docker_branch branch October 8, 2025 14:11
@github-actions github-actions bot mentioned this pull request Oct 8, 2025
@puehringer puehringer added release: patch PR merge results in a new patch version type: feature New feature or request labels Oct 8, 2025
puehringer added a commit that referenced this pull request Oct 8, 2025
* chore: prepare next dev release

* feat: make GIT_BRANCH and GIT_COMMIT_HASH available as env variables (#153)

Closes *list issues numbers here*

### Developer Checklist (Definition of Done)

**Issue**

- [ ] All acceptance criteria from the issue are met
- [ ] Tested in latest Chrome/Firefox

**UI/UX/Vis**

- [ ] Requires UI/UX/Vis review
  - [ ] Reviewer(s) are notified (_tag assignees_)
  - [ ] Review has occurred (_link to notes_)
  - [ ] Feedback is included in this PR
  - [ ] Reviewer(s) approve of concept and design

**Code**

- [ ] Branch is up-to-date with the branch to be merged with, i.e.,
develop
- [ ] Code is cleaned up and formatted
- [ ] Unit tests are written (frontend/backend if applicable)
- [ ] Integration tests are written (if applicable)

**PR**

- [ ] Descriptive title for this pull request is provided (will be used
for release notes later)
- [ ] Reviewer and assignees are defined
- [ ] Add type label (e.g., *bug*, *feature*) to this pull request
- [ ] Add release label (e.g., `release: minor`) to this PR following
[semver](https://semver.org/)
- [ ] The PR is connected to the corresponding issue (via `Closes #...`)
- [ ] [Summary of changes](#summary-of-changes) is written


### Summary of changes

- Requires datavisyn/github-workflows#219
- Makes GIT_BRANCH and GIT_COMMIT available if they are set in the
environment

### Screenshots


### Additional notes for the reviewer(s)

-  
Thanks for creating this pull request 🤗

* Prepare release version 13.2.3

---------

Co-authored-by: datavisyn-bot <>
Co-authored-by: Michael Pühringer <51900829+puehringer@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release: patch PR merge results in a new patch version type: feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant