Support for authenticating to private action repos

Open
#49 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, github, shell

Research direction

Start by tracing the script's git remote and fetch commands shown in the issue, then inspect how credentials or git options are currently passed. Done means internal or private action repositories can be cloned successfully while public repository behavior continues to work.

Written by the indexing model from the issue text.

Description

Using this inside of an organisation where the actions repo are internal or private the scripts are unable to clone the git repo as it expects them to be public.

Any chance we can add a way to specify auth details to push through to git?

I may take a look if/when I get a chance but wanted to get any ideas on implementation first

This is what happens currently

EXEC: git remote add origin https://github.com/my-org/actions.git
EXEC: git -c protocol.version=2 fetch --tags --no-recurse-submodules origin
fatal: could not read Username for 'https://github.com/': No such device or address
ERROR: Command exited with code 128
Dominant language
Shell
Stars
64
Forks
17
Avg merge
1d 12h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/action-versions

All issues in actions/action-versions

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.