TEST4 Danielle's change 2 and ken's change

composite-run-steps-action-template

This template can be used to quickly start a new custom composite-run-steps action repository. Click the Use this template button at the top to get started.

Index

• Inputs
• Outputs
• Example
• Contributing
  • Incrementing the Version
• Code of Conduct
• License

TODOs

• Readme
  • Update the Inputs section with the correct action inputs
  • Update the Outputs section with the correct action outputs
  • Update the Example section with the correct usage
• action.yml
  • Fill in the correct name, description, inputs and outputs and implement steps
• CODEOWNERS
  • Update as appropriate
• Repository Settings
  • On the Options tab check the box to Automatically delete head branches
  • On the Options tab update the repository's visibility
  • On the Branches tab add a branch protection rule
    • Check Require pull request reviews before merging
    • Check Dismiss stale pull request approvals when new commits are pushed
    • Check Require review from Code Owners
    • Check Include Administrators
  • On the Manage Access tab add the appropriate groups
• About Section (accessed on the main page of the repo, click the gear icon to edit)
  • The repo should have a short description of what it is for
  • Add one of the following topic tags:

    Topic Tag	Usage
    az	For actions related to Azure
    code	For actions related to building code
    certs	For actions related to certificates
    db	For actions related to databases
    git	For actions related to Git
    iis	For actions related to IIS
    microsoft-teams	For actions related to Microsoft Teams
    svc	For actions related to Windows Services
    jira	For actions related to Jira
    meta	For actions related to running workflows
    pagerduty	For actions related to PagerDuty
    test	For actions related to testing
    tf	For actions related to Terraform

  • Add any additional topics for an action if they apply

Inputs

Parameter	Is Required	Description
input	true	Description goes here

Outputs

Output	Description
output	Description goes here

Example

# TODO: Fill in the correct usage
jobs:
  job1:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v2

      - name: ''
        uses: im-open/thisrepo@v1.0.0 # TODO: fix the action name
        with:
          input-1: ''

Contributing

When creating new PRs please ensure:

1. For major or minor changes, at least one of the commit messages contains the appropriate +semver: keywords listed under Incrementing the Version.
2. The README.md example has been updated with the new version. See Incrementing the Version.
3. The action code does not contain sensitive information.

Incrementing the Version

This action uses git-version-lite to examine commit messages to determine whether to perform a major, minor or patch increment on merge. The following table provides the fragment that should be included in a commit message to active different increment strategies.

Increment Type	Commit Message Fragment
major	+semver:breaking
major	+semver:major
minor	+semver:feature
minor	+semver:minor
patch	default increment type, no comment needed

Code of Conduct

This project has adopted the im-open's Code of Conduct.

License

Copyright © 2022, Extend Health, LLC. Code released under the MIT license.