2014: As commented in this “GitHub OAuth Busy Developer’s Guide” Tokens don’t have to expire. They only send back the access token and an expiration (field “expires_in“, seen as far back as 2013) if the offline_access scope is not requested (as it is the case for a refresh token). Right now, GitHub just assumes all … Read more
I have encountered the exact same problem. I did manage to acquire all the commits for all branches within a repository (probably not that efficient due to the API). Approach to retrieve all commits for all branches in a repository As you mentioned, first you gather all the branches: # https://api.github.com/repos/:user/:repo/branches https://api.github.com/repos/twitter/bootstrap/branches The key that … Read more
This will have to be relative to a particular commit, as some files may be present in some commits and absent in others, so before you can look at files you’ll need to use something like List commits on a repository: GET /repos/:owner/:repo/commits If you’re just interested in the latest commit on a branch you … Read more
I use the following script: git log main –first-parent –merges \ –pretty=format:”%h %<(10,trunc)%aN %C(white)%<(15)%ar%Creset %C(red bold)%<(15)%D%Creset %s” Explaining each argument: main: the name of your main branch. Can be omitted, in which case the current branch will be used. –first-parent: skips commits from merged branches. This removes the entries where someone merged master into their … Read more
From Official GitHub: Releases are GitHub’s way of packaging and providing software to your users. You can think of it as a replacement to using downloads to provide software. With Releases, you can provide links to binary files, as well as release notes describing your changes. At their core, Releases are based on Git tags. … Read more
I found out why this occurs and how to resolve it. According to the docs: Note: The returned email is the user’s publicly visible email address (or null if the user has not specified a public email address in their profile). In your GitHub profile settings, under Public email, some users (including myself) have that … Read more
Everything you are doing is OK. However, when creating OAuth tokens for authentication, be sure that you are defining the right scopes. Each scope defines a specific set of permitted actions (information you can read/write), so you should check that you are creating the token with the repo scope.
A workaround would be to create a public repo, composed of: empty commits (git commit –allow-empty) each commit tagged each tag with a release each release with the deliveries (the binaries of your private app) That way, you have a visible repo dedicated for release hosting, and a private repos for source development.
This is for developers registered to the GitHub Developer Program (like this GitHub profile, for instance) Membership is open to individual developers and companies who have: A paid GitHub.com personal or organization plan (since 2019, you don’t need a paid membership anymore) An integration in production or development using the GitHub API An email address … Read more