Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api | ||
ci/api | ||
projects | ||
shared | ||
git_http_spec.rb | ||
jwt_controller_spec.rb | ||
lfs_http_spec.rb |
BigW Consortium Gitlab
So if we also query against SHA, we could actually support SHA. If there's a branch or tag also named like SHA this could be ambiguous, but since we could already do that in Git, I think it's probably fine, people would be aware they shouldn't use the same name anyway.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api | Loading commit data... | |
ci/api | Loading commit data... | |
projects | Loading commit data... | |
shared | Loading commit data... | |
git_http_spec.rb | Loading commit data... | |
jwt_controller_spec.rb | Loading commit data... | |
lfs_http_spec.rb | Loading commit data... |