Hi, I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image). If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work. One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team