port-labs/Port Cookiecutter Action

GitHub action to create repositories templated with Cookiecutter with Port integration

Trust Signals

workflow.ymlSHA-pinned

uses: port-labs/cookiecutter-gha@7c38e1106a6f2bb8b7df031d943ae99ec5102860 # v1.2.2

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
token	The GitHub Token to use to authenticate with the API with permissions to create repositories within the organization (supporting only PATs at this time)	yes	—
portClientId	The Port Client ID to use to authenticate with the API	yes	—
portClientSecret	The Port Client Secret to use to authenticate with the API	yes	—
blueprintIdentifier	The blueprint identifier to use to populate the Port	yes	Service
repositoryName	The name of the repository to create	yes	—
repositoryType	The type of repository, public or private	yes	private
organizationName	The name of the organization to create the repository in	yes	—
cookiecutterTemplate	The cookiecutter template to use to populate the repository	yes	—
portUserInputs	Port user inputs to came from triggering the action	yes	—
githubURL	GitHub URL. Default value is taken from context	yes	${{ github.server_url }}
githubAPI	GitHub API URL. Default value is taken from context	yes	${{ github.api_url }}
portRunId	Port run ID to came from triggering the action	yes	—
monorepoUrl	The URL of the monorepo to create the new service in, specify it alongside scaffoldDirectory to open a new pull-request in the monorepo	no	—
scaffoldDirectory	The directory to scaffold the cookiecutter template in	no	—
templateDirectory	The directory to scaffold the cookiecutter template from	no	—
createPortEntity	Whether to create a Port entity for the repository	no	true

no outputs