You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to be able to tag a build. This could be a git tag, but probably not because that could interfere with v0.1.0.
What I really want is, to just tag a build as something, for easy reference later. For example, I'm working with a PM and I'm showing him two different versions of the product. They're both master branch, because it just so happens that one of the earlier versions had a different UI. So now I'm just sharing my.app.com and my.app.com?build_id=26. But I have to find those in the admin, and remember htem in my head, which one's which.
What I really want is, in the admin UI, to tag 26 as "horizontal_layout" and tag 33 as "veritical_layout". Then in the admin, I want to be able to sort the builds table by only custom tags, and then have simple links to those two builds.
The links could still be &build_id=26, but it would be easy to find them in the admin, and easy to copy the link and share.
The text was updated successfully, but these errors were encountered:
I want to be able to tag a build. This could be a git tag, but probably not because that could interfere with
v0.1.0
.What I really want is, to just tag a build as something, for easy reference later. For example, I'm working with a PM and I'm showing him two different versions of the product. They're both master branch, because it just so happens that one of the earlier versions had a different UI. So now I'm just sharing my.app.com and my.app.com?build_id=26. But I have to find those in the admin, and remember htem in my head, which one's which.
What I really want is, in the admin UI, to tag 26 as "horizontal_layout" and tag 33 as "veritical_layout". Then in the admin, I want to be able to sort the builds table by only custom tags, and then have simple links to those two builds.
The links could still be
&build_id=26
, but it would be easy to find them in the admin, and easy to copy the link and share.The text was updated successfully, but these errors were encountered: