I’ve added support to select either Sandbox or Production (Developer) login, there is now a main page where you can enter the owner and repository name manually. If passed in the URL these fields will be populated automatically.
The original URL format is still supported, but only deploys to production…
To generate a URL that will only deploy to sandbox…
To generate a URL that will display the above page and give the user the choice.
To display the main page without any default owner or repository simply use this..
Pingback: Deploy direct from GitHub to Salesforce! | Andy in the Cloud
December 12, 2013 at 10:58 am
Reblogged this on Sutoprise Avenue, A SutoCom Source.
March 26, 2014 at 7:57 pm
This is brilliant but I’m getting the following error when trying to deploy to Sandbox. “Application Error
An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.” Is this working for anyone else?
March 26, 2014 at 8:05 pm
Is this sandbox or production your deploying to? Also can you share your deploy URL so I can test. Thanks!
March 26, 2014 at 8:08 pm
Sandbox. Here is the URL I’m using: https://githubsfdeploy-sandbox.herokuapp.com/app/githubdeploy/mechen8/scorecard
March 26, 2014 at 8:45 pm
Strange, the Heroku app had got itself in a failed state (just the sandbox one). I have restarted it now and it seems to be responding. First time since December its needed attention…
March 26, 2014 at 8:48 pm
Works now. Thank you for this.
September 17, 2014 at 3:13 pm
Is there a reason this is married to GitHub? Could it work on repos held elsewhere just as easily?
September 17, 2014 at 9:32 pm
No reason, so long as there is an API. What others do you have in mind?
September 17, 2014 at 10:28 pm
I have a Bitbucket repo and another repo on my linux box that I hit w/SSH. Thanks.
February 29, 2016 at 12:53 am
Hi Andrew, I tried using the sandbox link and it shows the below error message.
classes/SObjectDataLoaderTest.cls(521,87):Method does not exist or incorrect signature: [SObjectDataLoader.SerializeConfig].addToUserFieldBlackList(Map>)
February 29, 2016 at 9:06 am
This looks like a bug in the code, can you raise a GitHub Issue and me or someone will take a look.
March 2, 2016 at 3:01 am
Thanks for your reply. I raised a bug here. Do you think it will be available for use anytime soon?
April 5, 2016 at 7:57 pm
This is great.
Is Lightning/Aura not supported? I receive this error: “The prefix “aura” for element “aura:application” is not bound.”
April 5, 2016 at 8:18 pm
Yes it should be, is the file valid if you save it via one of the Salesforce editors? If so, raise a GitHub issue with the repo name and I will take a look.
May 5, 2020 at 3:53 pm
i have the same issue “The prefix “aura” for element “aura:application” is not bound” i’m working with vsCode !
May 9, 2020 at 6:47 am
I am guessing this a vscode only error and your push or deploy will he fine. I think it’s basically looking for a valid xml namespace declaration for aura and since those are typically not included in an aura markup you are getting this error. Just a theory.
July 14, 2016 at 9:15 am
Is this deployment tool working also with bitbucket? Or can I make something to make it work in bitbucket? Thanks.
July 15, 2016 at 12:11 pm
This has been on the enhancements list for a while. It’s not often the request comes up for this support to be honest. The project is open source, so it would be great if your able to contribute code to add this. Sorry in the meantime, bit bucket is not supported. Andy
August 26, 2016 at 9:16 am
Hi @andreww : I was trying to deploy feature branch of repo. Is it possible?
August 21, 2018 at 12:02 am
@andreww: Thanks for the great tool. I´m having problems deploying to any Sandbox. I´m always getting an oAuth Error:
1800 : There was a problem in setting up your remote access
December 15, 2018 at 2:10 pm
Thanks i am also getting other reports. I’ll take a look.
February 21, 2019 at 10:45 am
Any solution to the Oauth?
April 23, 2023 at 5:47 pm
This has been fixed in the latest releases
July 31, 2019 at 3:29 am
Hello Andrew, hope you are doing well. I am also getting oauth error while logging in to sandbox. Any help is appreciated.
September 2, 2019 at 8:31 am
You need to speak to your admin, there are connected app settings in the org that they must have used to block this app