SAS Enterprise Guide

Desktop productivity for business analysts and programmers
BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Sajid01
Meteorite | Level 14

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?

1 ACCEPTED SOLUTION

Accepted Solutions
dazimm
SAS Employee

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

View solution in original post

2 REPLIES 2
dazimm
SAS Employee

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

Sajid01
Meteorite | Level 14

Thanks for the quick reply.

sas-innovate-white.png

Our biggest data and AI event of the year.

Don’t miss the livestream kicking off May 7. It’s free. It’s easy. And it’s the best seat in the house.

Join us virtually with our complimentary SAS Innovate Digital Pass. Watch live or on-demand in multiple languages, with translations available to help you get the most out of every session.

 

Register now!

Creating Custom Steps in SAS Studio

Check out this tutorial series to learn how to build your own steps in SAS Studio.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 2 replies
  • 1306 views
  • 0 likes
  • 2 in conversation