tag:help.appveyor.com,2012-11-13:/discussions/problems/25488-apparent-inconsistency-between-github-notifications-and-github-releasesAppVeyor: Discussion 2019-11-26T06:10:15Ztag:help.appveyor.com,2012-11-13:Comment/478562442019-11-25T18:36:04Z2019-11-25T18:36:04ZApparent Inconsistency Between GitHub Notifications and GitHub Releases<div><p>Hi Mike,</p>
<p>There is a pre-defined OAuth token for GitHub notifications, kind of "AppVeyor Bot". For GitHub Releases you should use your own token to publish on behalf of your team.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/478562442019-11-25T20:26:09Z2019-11-25T20:26:09ZApparent Inconsistency Between GitHub Notifications and GitHub Releases<div><p>By token on behalf of my team, are you meaning Personal Access Token? As those cannot be limited and filtered to a particular repo, I would, of course, very much prefer to utilize a repo-specific and targeted mechanism as the one employed by Notifications.</p>
<p>If you are saying this is not possible/available, I would be OK with having it put on "the TODO list" for a future release/version. :)</p></div>Mike-Etag:help.appveyor.com,2012-11-13:Comment/478562442019-11-25T23:59:43Z2019-11-25T23:59:43ZApparent Inconsistency Between GitHub Notifications and GitHub Releases<div><p>Yes, I mean PAT. I agree it's an absolutely annoying limitation that PAT impersonates the user and provides access to all their repositories. That was the motivator for GitHub to introduce GitHub Apps. However, right, GitHub App token could not be "generated" as PAT and even API easily. We've used to recommend customers creating a new GitHub user (so called CI bot) and giving them precise access to only selected orgs/repos, though that requires another user/seat license. The solution worked well before GitHub changes pricing to per-user.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/478562442019-11-26T06:10:08Z2019-11-26T06:10:08ZApparent Inconsistency Between GitHub Notifications and GitHub Releases<div><p>Yeah, alright. That works for me. You are aware of the problem and the associated annoyances with it.</p>
<p>Maybe it might be worth looking into creating a GitHub app to see if it can do what we want to accomplish. Seems like they would simply provide a further field on the PAT to limit its scope. Such a hassle.</p>
<p>Anyways, the rest of your service is remarkable. You have a lot to be proud of here!</p></div>Mike-E