Auto-configure Bug tracker for new repos/Products #15
Comments
atodorov
added a commit
that referenced
this issue
Jul 12, 2020
when a new repository is added on GitHub Kiwi TCMS will create a bug tracker integration record in its DB pointing to the same repository and using the existing integration class.
atodorov
added a commit
that referenced
this issue
Jul 13, 2020
this should fail b/c the payload is missing the `full_html` field
atodorov
added a commit
that referenced
this issue
Jul 13, 2020
this should fail b/c the payload is missing the `full_html` field
atodorov
added a commit
that referenced
this issue
Jul 21, 2020
this should fail b/c the payload is missing the `full_html` field
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a new product is added to DB (e.g. on a new repo hook) we can configure new bug trackers to GitHub Issues for that particular repository/product. This is very straight forward.
The difficult part lies in the fact that we need a personal access token (with the repo (write)) permission so we can file issues on behalf of the user automatically. PyGithub supports API authentication with client_id/secret but according to GitHub's API docs:
https://developer.github.com/v3/#oauth2-keysecret this will only serve to increase API limits.
The app integration needs to somehow create an access token that would be used when communicating with the GitHub API.
The text was updated successfully, but these errors were encountered: