fletort/Init Repository
Internal Action to Init My repositories following internal rules.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Nov 22, 2024
- License
- MIT
Pinned Snippet
uses: fletort/init-repo-action@25f2a30b6f977dd57714ed89c2274d2bc98eb6bd # v1.7.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| repository | Repository Name to init. Indicate the repository name with owner. For example owner/my_project | — | ${{ github.repository }} |
| template | Template to use to init the repository (use only if repo is not already created) | — | no_init |
| repository_deployment | Repo on which we want to make deployement. For example owner/my_published_repo. If not specified, the deployment feature is not initialized. | — | — |
| token | Personal access token (PAT) used to: - create the repository (if requested). - fetch the repository - store secret inside the repository And add publish key to repository_deployment - create a MR on the repository We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary. | — | — |
| testspace_link_enable | Indicates if the testspace link feature is enable. If set to `true` the `testspace_token` attribut is *mandatory*. Default is `false`. | — | false |
| testspace_token | Personal testspace token used to interact with the testspace API to create the project. *Mandatory* is the testspace feature is enable with the help of the `testspace_link_enable` attribut. | — | — |
| testspace_domain | Testspace SubDomain | — | ${{ github.repository_owner }} |
| delete_workflow | — | — | true |
| j2_keep_template | Put to `true` to keep original template jinja2 file. | — | false |
| j2_data_file | Source file contening inputs variable for the jinja2 templates. | — | "" |
| j2_data_format | Format of the `j2_data_file`. Can be `env`, `ini`, `yaml`, `json` or `automatic` (for automatic detection). The automatic detection is based on the extension then on the content. | — | automatic |
| j2_data_url | URL Link contening inputs variable for the jinja template. | — | "" |
| j2_data_url_format | Format of the `data_url`. Can be `env`, `ini`, `yaml`, `json` or `automatic` (for automatic detection). The automatic detection is based on the http header content-type then on the content itself. | — | automatic |
| j2_undefined_behaviour | — | — | — |
| base_branch | Base existing branch use to start the work. Usefull only on `not created` repository. If not defined, the default branch is used. | — | — |
| branches | JSON or YAML branches description. The definition can be directly done, through a local file or a distant one (web link). | — | automatic |
| branch-before | Branch to create on the base branch before the commit | — | — |
| commit-message | The message to use when committing changes | — | [init-repo-action] Dynamic Template Resolution |
| commit-branch | Branch where commit will be done. Default Value depends of the context. On a PR new branch "template_resolution" is used, outside a PR, base_branch is used. | — | — |
| pr-created | Indicates if a pr is created | — | true |
| pr-title | The title of the pull request. | — | Dynamic Template Resolution |
| pr-body | The body of the pull request. | — | Jinja2 Template Resolution made by jinja2-template-action |
Outputs
| name | description |
|---|---|
| testspace_space_id | The testspace space id created |