I’m trying to setup a new project via Github App (not Github OAuth App) following the instructions found in docs>create-project>#create-a-project
Per the instructions, I created and added a SSH deploy key to Github (pub) and CircleCI (private). Clicked create and a loader popped up for a second or so but there was no page transition or confirmation. I decided to wait a bit and in the meantime confirmed that the CircleCI Github App was installed for my selected repo in Github. For reference, I gave read access only to a single repo.
By this time the create project screen had not transitioned. I was expecting it to take me to a page where I could setup a basic config because I selected the “Fast” option instead of “Faster”, and the former said it would take me to such a screen. I opened a new window and saw that the project was created. However, when I go to the “Configuration” section I don’t see the Github App as an option, instead I see a button to “Set Up Configuration”. Clicking that leads me to an “Add configuration screen” but with a dropdown containing only Gitlab sources.
This is my second attempt at creating a basic project. I’ve used CircleCI in the past with no issues, but that was a few years ago with Github OAuth. Do I need to give it write permission? If so why even have it as an option? Any insight would be much appreciated. Thank you!
I was able to setup a project with Github App by doing a fresh install and creating the project against a repo that already has an initial config.yml committed. From my experience, it looks like there might be an issue with the project onboarding process on the config / web config editor step.
However, when I go to the “Configuration” section I don’t see the Github App as an option, instead I see a button to “Set Up Configuration”. Clicking that leads me to an “Add configuration screen” but with a dropdown containing only Gitlab sources.
Do you remember if in the “Triggers” section of the Project Settings, there was a “GitHub App trigger” listed? All good if not. The path you described should work, but the “trigger” needs to be created first in order for the “Configuration” section to have anything populated.
No, there was no “GitHub App trigger” in the “Triggers” section. That section required a configuration, and there was only a button that when clicked led to the setup configuration screen. So it was implied that a configuration was first required before a Trigger could be added.
Got it, thanks for clarifying. We’ll look into whether there’s a bug with the flow that takes you to the in-app config editor. Don’t hesitate to reach out if you run into any additional issues.
During this process I created two projects that I wish to delete. I can only find an “Unfollow” mechanism which seems to remove them from the feed/dashboard and not actually delete. Is there a self-service way to remove projects or do I need to contact support for this? If so, what is the best way to go about this?
We are working on enabling the ability to delete the project for users that use GitHub App, it is not currently available. For now, the recommended workaround is to remove the repository from the scope of the GitHub App installation which I believe can be done on the GitHub side of things.
When we have a mechanism to self-serve delete projects, I’ll let you know and it’ll be reflected on our docs as well. cc @spencer.franks