Explore the Automated Process for Tag Generation about cti-website-frontend HOT 4 CLOSED

GitHub Developer Documentation link updated in the issue's resources.

from cti-website-frontend.

I can use my personal-access-token to hit the replace all repository tags API endpoint https://developer.github.com/v3/repos/#replace-all-repository-topics
But when I use the access-token generated by GitHub App(steps in StackOverflow question) I get the following:

{
    "message": "Resource not accessible by integration",
    "documentation_url": "https://developer.github.com/v3/repos#replace-all-topics-for-a-repository"
}

To describe my issue, refer the question on StackOverflow(the question talks about consuming issues GitHub API but the scenario is entirely the same with the API that I am trying to consume) https://stackoverflow.com/questions/51336005/github-api-what-permission-should-a-github-app-get-when-create-an-issue

Resolution
Trying to find a solution/workaround

from cti-website-frontend.

Functionality achieved

OAuth Application created for Civic Tech Index Organization.

Steps to replicate the demo:

1. In a browser window, open the link
2. Authorize the OAuth Application
3. Grab only the query parameter code from the URL
4. Using Postman, consume the following POST API endpoint:

https://github.com/login/oauth/access_token?client_id=8ce9dc8a15484de9060d&client_secret=4cec9b74ff3e912c354e8437dfb45303d2bb79a5&code=9496c118aec0f37d831b&redirect_uri=https://cti-dev.herokuapp.com/&state=j16nz4wntk

5. From the API response grab the access token
6. Consume the GitHub API - PUT Replace all repository topics
7. Use the access token as a Request Header for the above PUT API endpoint,

Key: Authorization, Value: Bearer <access-token obtained>

8. In the Body, switch to raw - JSON format and add the following:

{
  "names": [
	"civictechindex"
  ]
}

9. Hit Send Button
10. On a successful replace all repository tags functionality, the API should return status code 200 with response same as the body in step 8

Security concerns:

1. Client ID and Client Secret are exposed in PUT API call (step 4)
2. All of this needs to achieved using an interface/website -> initiation from Checkout out our automated process [Referring the Figma file]

from cti-website-frontend.

This issue can be closed as the GitHub Oauth App for civictechindex is configured and steps to replicate the automation of repository tags explained in the above comment

from cti-website-frontend.