- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hello
I was testing the new SASEG functions for git repository using the following
https://go.documentation.sas.com/?docsetId=lefunctionsref&docsetTarget=n10pxql65jtf4sn11m3d6jzcrgcz....
AND
and https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2019/3057-2019.pdf.
All the codes are from the above paper. They work straight out of the book with appropriate modifications for local paths.
(Thanks Zimmerman for such a nice paper)
The code works fine with the repository .(SGF2019) mentioned in Zimmerman's paper
I am trying with bitbucket and my default repository is not master. It has the name develop.
I have checked out the develop repository and tried to get commit history and I cannot get it.
(I tried without checking out the develop repository- the error is the same)
The error is :
ERROR: Return code from GIT is (4). reference 'refs/remotes/origin/master' not found
There is no master and obviously I cannot get the history.
Any suggestions?
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi Somename,
First off, I'm happy that you like my paper!
So the 'refs/remotes/origin/master' is an issue with the GITFN_COMMIT_LOG function. I have addressed this issue for an upcoming release, but for the time being what you could do is create a remote master branch in bitbucket and then do a pull on your local repository. This will add the 'refs/remotes/origin/master' reference to the local repository the function is looking for. Then check out your development branch you have been using, and run GITFN_COMMIT_LOG function again.
Let me know if you have any questions.
Danny
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi Somename,
First off, I'm happy that you like my paper!
So the 'refs/remotes/origin/master' is an issue with the GITFN_COMMIT_LOG function. I have addressed this issue for an upcoming release, but for the time being what you could do is create a remote master branch in bitbucket and then do a pull on your local repository. This will add the 'refs/remotes/origin/master' reference to the local repository the function is looking for. Then check out your development branch you have been using, and run GITFN_COMMIT_LOG function again.
Let me know if you have any questions.
Danny
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the quick reply.