-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add New Connector - tap-google-search-console #55
Comments
@pnadolny13 @tayloramurphy not sure how to assign you but tagged |
I'm not familiar with Azure DEvOps, but they might have documentation on how to transfer a repository to GitHub. |
@acarter24 I think Azure DevOps is a standard git repository so I think an approach would be to mirror it and push that up to github. https://www.atlassian.com/git/tutorials/git-move-repository seems like a reasonable approach. I sent you an invite to collaborate on the new repo https://github.com/MeltanoLabs/tap-google-search-console |
Just FYI I have not forgotten about this :) I have friday this week set aside to work on it, mostly I will be getting code standards up to scratch with pre-commit and working on some tests. Hoping to have a version pushed that I can get some others to test. |
I have pushed an initial version for any comment or testing you can offer. I have been using this code in production for nearly 12 months, so happy it is stable for my setup, but good to get someone else to try it out. |
Thanks @acarter24! We'll get it added to the Hub. |
Hi, I have built a private tap for Google Search Console which I have been given permission to contribute to MeltanoLabs.
https://developers.google.com/webmaster-tools/v1/api_reference_index
At present the tap just exists on our private Azure DevOps server, but I would like to add to Meltanolabs and happy to act as maintainer.
I'm running through some of the guides on the Meta repo to get my private version up to snuff, what are next steps to allow me to push the repo to meltanolabs?
The text was updated successfully, but these errors were encountered: