Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Control the name of the forks #15

Open
rajbos opened this issue Nov 4, 2021 · 2 comments
Open

Control the name of the forks #15

rajbos opened this issue Nov 4, 2021 · 2 comments

Comments

@rajbos
Copy link
Owner

rajbos commented Nov 4, 2021

A lot of actions have a less descriptive name for the repo, since the owner part gives more information, for example:

 - uses: blackducksoftware/github-action
 - uses: actions/github-script

Forking them copies over the repo name, but doesn't capture their owners name, so the examples above become:

  - uses: rajbos-actions-test/github-action
  - uses: rajbos-actions-test/github-script

This is not very descriptive for the end user who need to add this into their workflows.

Proposal: add the owner- in front of the forked repo name so the examples become this:

 - uses: rajbos-actions-test/blackducksoftware-github-action
 - uses: rajbos-actions-test/actions-github-script

This will still not be a 100% solution, but already improves. Maybe we can add a parameter for it later, when we use an issue template for the requestor to follow.

@readefries
Copy link
Collaborator

Maybe use a ~ instead, as the - is already used in a lot of actions, and doesn't state which part is the action and which part is the owner.

@rajbos
Copy link
Owner Author

rajbos commented Nov 4, 2021

Maybe use a ~ instead, as the - is already used in a lot of actions, and doesn't state which part is the action and which part is the owner.

Good idea. ``` doesn't work unfortunately (check the hint in the image), so lets fall back to an _ then :-)
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants