1. Ganesan Rajan
  2. PowerBuilder
  3. Friday, 5 June 2020 13:02 PM UTC


I faced a hurdle when tried to push PB objects to Github repository.

I created a repo in my organisation's Github space. i.e github.mycompanyname.com

Actually when I login to the github.mycompanyname.com, it will ask for User Id and password and it will further open Mutifactor Authentication window. Upon entering security code, I will be able to get into github.mycompanyname.com

I opened my PB2017R3. Added objects to Git using Add to SOurce control.

Now I tried Git Push. It opens window to give repo URL, user id and password. I gave my newly created Repo URL, User id & Password. Clicked Test COnnection. I get the message saying "Failed to perform the specified operation. Please make sure you can connect to the server repository."

Actually I am able to connect to this repository using Chrome browser via Mutifactor Authentication as explained above.

Can you please let me know how to push the PB objects to my organisations Github repo?

Thanks in Advance,
Ganesan R

Accepted Answer
Ganesan Rajan Accepted Answer Pending Moderation
  1. Wednesday, 10 June 2020 13:37 PM UTC
  2. PowerBuilder
  3. # Permalink

Thank you Tom for your prompt reply.

We shall continue to explore further on this and I will open a separate thread, If I get more queries and doubts.



Ganesan R

There are no comments made yet.
Ganesan Rajan Accepted Answer Pending Moderation
  1. Monday, 8 June 2020 13:55 PM UTC
  2. PowerBuilder
  3. # 1

Thank you Tom. Your suggestion worked.

1. Should all my team members use the same token to access the code repository in GitHub?

2.I like to have Clarity on folder structure maintained when we add objects to Git.
Actually in VSS, each PBL will be in a folder in my local machine and that folder may or may not have all objects like windows, DWs etc.

Shouldn't we maintain that structure in Git?

After Git Push is done, PB creates ws_objects folder. Is there any help available to understand how to maintain folder structure in PB anf Git environment?

3.After I pushed my objects to Github, It is all stored in master repo in GItHub. When each developer connect to that repo via PB and work on individual enhancements, Will they need to create a branch and commit the changes into that branch first? Only then it should be moved to local master and then to Origin master in Github?

I like to know how to switch between branches within PB IDE?

Because when I do commit, it directly commits to local master and then Git Push, moves it to Origin master in Github. Is it safe to do this way OR do you suggest any better workflow.

Sorry for too many questions.

If you can kindly answer these questions, it will be of great help.

Thanks a ton

Ganesan R

  1. Tom Jiang @Appeon
  2. Wednesday, 10 June 2020 05:47 AM UTC
1. You may create a unique token for each member. Or you may add each member as a contributor to the repository on GitHub, so they could use their own credential or PAT to access the repository.

2. With VSS you have to put each PBL in a separate folder. Otherwise, all objects will be exported to the same root folder and objects with the same names will be overwritten. The new Git integration automatically creates a subfolder inside ws_objects for each PBL, so you don't have to put each PBL in a separate folder. But if you have already put PBLs in a separate folder, it will still work. It's just that it will be one level deeper in the ws_objects folder.

3. You may refer the following link for working with branches:


Notes: there is a plan to add branch operation within PB IDE in a future release of PB 2019 R3.
  1. Helpful
There are no comments made yet.
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Monday, 8 June 2020 03:14 AM UTC
  2. PowerBuilder
  3. # 2

Hi Ganesan,
You can authenticate using a personal access token (PAT). Basically, you can generate a PAT on GitHub and use it as both your user name and password in PB IDE.
Username: yourPAT
Password: yourPAT
You can refer to the following link for more information:
Notes: Remember to give access to your repositories when creating the PAT.
Tom Jiang

There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.