Hi Support team,
I just bought Monster Markdown and I'm trying to sync with my new git repo in github. But it doesn't seems to be working. Could you please help me with it.
I executed following steps to sync my new repo in Github.
- create a repository in GitHub
- Create local git repository. File -> Git -> Create Repo
- Sync with Remote ( newly created ) Git repository in Github. File -> Git -> Attach to remote repo.
- Commit. File -> Git -> Commit -> Commit and Push.
Thanks Shrijan
Hi Cjan,
Best thing to do is check and make sure that the Git Repository is properly connected externally. Can you push/pull with Git from the command line or another tool?
+++ Rick ---
Thanks Rick,
It didn't work for me.
I no longer need this software. Is it possible for you to refund my money?
Thanks Shrijan.
Did you check the documentation here:
Attaching a remote can be tricky, especially if the remote repository requires credentials and your local Git installation isn't set up for automatic authentication via Git Credential Store. If you're using Git with Github typically your account has a one time token applied as you've signed in and that token is stored on the machine. This process works across Git tools, but it's not very reliably in tooling. In theory when you connect and there is no authentication an authentication dialog should pop up, but this may or may not happen.
The workaround for this is to connect the remote via Git Command line (which will prompt for credentials) or another tool (like Github Desktop, SmartGit, SourceTree, GitKraken etc.) and if necessary set cached git credentials for the repository. Once the authentication is hooked up Git remote operations will work on all applications - including Markdown Monster - across machines.
To configure the credential manager that should help with connecting a remote and getting the authentication to work:
git config --global credential.helper manager
git config --system credential.helper manager
Then performing any command on the remote should prompt for authentication and once the right credentials have been supplied they should be cached.
To be honest I find this difficult to work with as well. Understanding when and how Git authenticates is a mystery, but once the initial connection has been made it (which can be messy as described above) all subsequent operations then use the cached credentials.
+++ Rick ---
thank you for quick response.
After evaluating and going through my need. I feel I'm ok with free opensource version of Markdown, and beside that I'm using other tool. Is it possible from you to refund my purchase. It will be very kind of you.
Many Thanks Again
Generally we don't offer refunds because we provide fully functional evaluation versions that allow anybody to check out all the features of products without having to purchase.
+++ Rick ---
HI Rick,
since I'm not using this software. could you please kindly consider to refund of the purchase. My apology for it. I haven't used more than a days. Please consider to refund.
thanks Shrijan