-
-
Notifications
You must be signed in to change notification settings - Fork 305
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
Document and show repo tags in the UI #6170
Conversation
Signed-off-by: Christoph Rueger <[email protected]>
Signed-off-by: Christoph Rueger <[email protected]>
Signed-off-by: Christoph Rueger <[email protected]>
Signed-off-by: Christoph Rueger <[email protected]>
Signed-off-by: Christoph Rueger <[email protected]>
Signed-off-by: Christoph Rueger <[email protected]>
@juergen-albert since you brought up the usecase of excluding the baseline repo, maybe you could do a quick review of the docs |
The documentation looks solid. Digging into this again, I have one remark and one possible change request. Remark: We should not use Possible change request or something for an additional issue: It would be nice to have something like |
Thanks @juergen-albert . The empty was a suggestion by @pkriens when we had a call about it. My suggestion: for the sake of this current PR we keep
Same here. I would suggest creating a new issue. I had something like this in the beginning but removed it during the discussion about the first version of this feature. Basically what I added was that you could specify a tag in -runrepos like this: |
Okay. Then +1 from me! |
And thanks heaps again. This feature is highly appreciated. |
Thanks for merging @juergen-albert 👍 |
added the link to the docu to the 7.1.0 release notes |
In this PR
-runrepos
)