I've never had to use a token to clone a repo. I just did this yesterday with the loader repo that Heimir created. I just looked in "Code" for the URL to clone. So for pacsatx, it should be

git clone https://github.com/AMSAT-NA/PacSatx.git

Checking something in is a different ball of wax. However, by "normal" personal access token, created in my own account about the time that github stopped allowing the normal password for checkins, seems to work fine. There is also the public key method, but I think you have to mess around with your local git to make that work. Or something. It works for the repos in my own area, but not for the AMSAT-NA repos.

73,

Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*

On Wed, Mar 1, 2023 at 8:43 AM Jonathan Brandenburg via pacsat-dev < pacsat-dev@amsat.org> wrote:

I am happy to have a look at it. Can you remind me of your environment, please?

Are you Windows, Mac or Linux?

Are you using command line, web interface, or a Git client (like TortoiseGit)?

Is your personal access token one of the fine-grained tokens? (There are a little tricky to use interactively but it can be configured. They must be given access to each individual API call as they are designed for automatic scripts.) Or is this a "classic" personal access token? (I know those are discouraged because of the ability for "lateral movement" between repositories in an organization.) Or, are you using 2FA? (I believe 2FA is the preferred mechanism for interactive human access).

Thank you!

Jonathan On 2/28/23 20:51, Bob Stricklin via pacsat-dev wrote:

All,

I continue to have an issue writing to the PacSatx repository. Jonathan has adjusted permissions to give me write access. Apparently there is more to it in this case. My use of git has mostly been with a repository I setup or one a company had. In this case it seems several here have owner rights in this repository.

I have tried with one of my personal access Tokens, but I have seen this from GIT:

Each token can only access resources owned by a single user or organization. Each token can only access specific repositories. Each token is granted specific permissions, which offer more control than the scopes granted to personal access tokens (classic). Each token must have an expiration date. Creating a personal access token - GitHub Docs https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#:~:text=Each%20token%20can%20only%20access%20resources%20owned%20by,%28classic%29.%20Each%20token%20must%20have%20an%20expiration%20date.

I have also read it may be possible to access a GIT if you have a project Token and create access with that using:

git clone "https://my-project:$PROJECT_TOKEN@my.gitlab.host/my-group/my-project.git"

Would anyone that knows the process on how to do this please help with the steps or send me the needed Token so i can gain access?

Thanks,

Bob

---

pacsat-dev mailing list -- pacsat-dev@amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

-- Jonathan Brandenburg Radio Amateur Satellite Corporation 1-214-213-1066

---

pacsat-dev mailing list -- pacsat-dev@amsat.org View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave@amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org