-
Notifications
You must be signed in to change notification settings - Fork 4
git clone/checkout fails when using commit sha1 as tag #106
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
Comments
Hm... this does already work. At least in the integration test. |
All pmd-regression-tester does, is executing:
And that works fine. Git checks out in detached mode. |
Ok, so it works for https://github.com/SalesforceLabs/Schedul-o-matic-9000 because "6b1229ba43b38931fbbab5924bc9b9611d19a786" is the latest commit referenced by HEAD: https://github.com/SalesforceLabs/Schedul-o-matic-9000/commits/master As soon as a new commit is added, it'll stop working. For the other repo https://github.com/apex-enterprise-patterns/fflib-apex-common we use the commit "7e0891efb86d23de62811af56d87d0959082a322", which is not the HEAD, and hence it fails:
|
Currently we need to fork Schedul-o-matic-9000 and fflib-apex-common in order to create a tag, that we can use in project-list.xml:
It would be nice to allow to specify directly a sha1 for the commit, e.g.
Using the
tag
-tag would avoid to change the schema for this file.The text was updated successfully, but these errors were encountered: