Ability to add a specific revision from a local git repository

[kalvenschraut]

My repository is a monorepo on local gitea instance we are self hosting. I want to be able to specify the specific commits that effect the specific project the release is being created for because not all commits in the tree may have affected the specific project/app.

I can pretty trivially figure out what commits are relevant, but doesn't seem to be a way to tell set-commit to just mark a specific revision as part of the release.

[kamilogorek]

https://docs.sentry.io/product/cli/releases/#sentry-cli-commit-integration

In case you are deploying without access to the git repository, you can manually specify the commits instead. To do this, pass the --commit parameter to the set-commits command in the format REPO_NAME@REVISION. You can repeat this for as many repositories as you have:

Isn't this what you are looking for?

[kalvenschraut]

We don't have a repo based integration, unless I am mistaken you don't integrate with a locally hosted gitea

I tried doing ORIGIN@REVISION since that came up in the repo list command but my commits are not associated to the release.

above is using the --auto flag. It is grabbing commits that actually didn't affect this specific project since the repo is a monorepo

above is my attempt at use ORIGIN@REVISION it did output the below but it didn't attach to the release. I want to be able to just associate specific revisions in my local repo to the release.

[github-actions[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[kalvenschraut]

Is this something that can be done or looked into in the future? As is I can't correctly associate commits with releases