I am trying to transfer ownership of a repo that I started to another github account. I get the notice in my gaining account that asks for permission of transfer. I click on the link in the email. Github responds with "Sorry, this repository transfer can’t be finished." Is there a source to figure out why?
I just successfully transfered my first repo just before trying this repo and everything went good. successful transfer. Just having problems with this second one.
Seems like for me, the problem was that I needed to log into the receiving account before accepting from the email.
I mistakenly solved this by clearing browser cache in IE. Too simple.
Related
I am doing an exercise where I've a forked repository, and started a heroku account, did "create a new app" and "deploy with github" but when I go to connect to github, a red error message pops up saying "Error: remote could not connect or was closed."
I have had no problems connecting github to other services, and I've found other people with connection issues, but more along the lines of "why isn't my app working" and mine is" why can't i link the two so I can continue with this exercise?"
Any help is greatly appreciated.
I've followed the instructions after setting up a heroku account, having an app repository fork on github, confirming my email, "create a new app" option on heroku, and on the ensuing "deploy" tab, clicked on the "connect github" option. I expected it to work.
Yes this is a known issue and caused by some data breach related to Github Authorization. Security measures have taken place and Github authorization has been disabled until further notice. Please see
https://github.blog/2022-04-15-security-alert-stolen-oauth-user-tokens/
And based on this ongoing incident,
As reported yesterday, revocation of all OAuth tokens from the Heroku
Dashboard GitHub integration is complete. Until further notice, we
will not issue OAuth tokens from the Heroku Dashboard. These actions,
based on our current understanding of the issue, should prevent
unauthorized access to your GitHub repositories.
We will continue to work with GitHub to provide additional guidance on
how to review your GitHub logs for evidence of exfiltration or
malicious activity. Please reach out to security#salesforce.com with
any information that may assist us with our ongoing investigation.
Please continue to visit status.heroku.com for the latest updates.
If you still want to deploy, you can switch from GitHub to Git quite easily, please read this: https://help.heroku.com/CKVOUPSY/how-to-switch-deployment-method-from-github-to-heroku-git-with-all-the-changes-app-code-available-in-a-github-repo
It is time we enabled the Continuous Integration of the build pipeline, so when I went to do just that, i am seeing something strange...
The trigger appears to be enabled? yet theres a message suggesting webhooks are missing to the repo and need to be restored. When i click restore, it fails!
The remote repository’s webhooks are missing or incorrect.
An error occurred while restoring the trigger’s webhook: Could not recreate the subscription. An error was encountered while creating the existing subscription: Unable to configure a service on the selected Bitbucket repository. Bitbucket returned the error 'Your credentials lack one or more required privilege scopes.'.
I asked the admin of the repo to try restoring it because i thought maybe this is a permissions issue, and even he got the error...
This is what the repository settings page shows for both myself and the repo developer/admin...
Do we have to add a webhook manually on bitbucket?
After debugging the issue further with the developer, it appears the app password we created in bitbucket may not have had the "Webhooks" option enabled.
Unfortunately, we cannot edit app passwords in Bitbucket, which is a bad constraint but whatever.
We ended up just creating a new app password, and enabled Webhooks permissions this time, then i updated the service connection with this new app password, and wala, it worked!
First of all, I'm not sure if this is the place to post this, but this is my last stop to get this fixed.
I've been trying to connect a Slack WebHook with a GitHub repository and I fail every time.
The steps I followed:
Create a webhook (both individually and using a new slack app) Copy
Copy the hook URL and paste in the new hook option in the GitHub repo.
Then when I create it, it gives me an error.
BTW, what should I add to the "Secret" field?
Please check the screenshot for more info.
Then I get the below error.
Let me know if I'm doing something wrong.
Not sure if this is still valid, but as I am also trying to create this connection, I found a possible solution in the GH Marketplace: https://github.com/marketplace/actions/slack-webhook-for-github-actions
I'm trying to fix up a broken Travis CI build script on a repo I was added to as a contributor. Everything works fine in the actual build, but trying to upload the build results to GitHub is broken.
The .travis.yml file contains an OAuth token which it puts into the Environment, and at the end it runs a script that retrieves this environment variable and uses it to upload the build output to GitHub. This is failing with a 401 Unauthorized error, which means the token is probably no longer valid.
I didn't write this up, and the way this works kind of bugs me. I'm not comfortable having authentication information in the repo, publicly accessible to the world, so it's just as well that this token is expired. But as I look things over, I don't see any better way to do this.
I need to do one of two things, either have the Travis build machine upload the build result to GitHub, or download the build result from Travis and upload it myself. Unfortunately, neither one seems to be a good option. No matter where I look on Travis CI's Web interface, I can't find any download link to retrieve the build results, which seems to rule out the second option. As for the first option, it doesn't appear that there's any way to perform the upload without the build machine having authentication information from the repository.
I can't be the first person to notice how problematic this is. I figure it has to be solved somehow; I'm just not sure how to fix it. Does anyone know how to resolve this?
If I try to click the “flip switch” next to a new repository in my Travis account, the flip switches but the hooks are never configured and I cannot trigger a build in Travis.
If I look at the console, I can read the following error:
XMLHttpRequest cannot load https://api.travis-ci.org/hooks/123456. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://travis-ci.org' is therefore not allowed access. The response had HTTP status code 500.
This may be linked to my GitHub organisation having activated third-party applications restrictions. Yet, all my previous repositories still build fine, and it's been weeks!
How can I start building a new repository in my Travis organisation account?
This is indeed linked to your organisation having third-party application restrictions, or “third-party whitelisting”.
You may not detect the problem at first since your current public repositories still receive web hooks, so it may be weeks before you get issues with Travis, and the connection with activation may be long lost in your mind.
So, now you've figured out these weird CORS/500 are linked to third-party application restrictions, you need to grant access to Travis again. But how? Travis has already been allowed access and won't ask you again for it upon login!
You have to go to your own user-approved application list in your GitHub profile, and click “View” next to the Travis-CI listing.
If you scroll down, you will get an “Organization access” listing. Your restricted organisation should be listed here, with a cross next to its name. Click “Grant access” to allow Travis into your org.
Everything should be in order now, and you should be able to activate Travis for your repo! You will just need to trigger a build by pushing a new commit after having “flipped the switch”.