semantic-release-conventional-config VS goals-template

open-sauced/semantic-release-conventional-config@v3 - semantic-release configuration, docker container and GitHub action

Release to npm from ghcr container:

Having previously dockerized our semantic release configuration in @open-sauced/semantic-release-conventional-config, a manual step was needed to publish the action in the GitHub marketplace.

The last thing that I learned about with this PR was some of the effects of "sprawl" of a project. In keeping with best practices, I created an issue first before creating the PR and by the time I was finished with the PR, I noticed there was already an issue in goals-template repo. This makes plenty of sense when you think about the ways that the Open Sauced project has grown.

// https://github.com/open-sauced/goals-template/blob/main/.github/workflows/sync-2-upstream.yml name: Sync to Upstream on: schedule: - cron: '0 7 * * 1,4' # scheduled at 07:00 every Monday and Thursday workflow_dispatch: jobs: sync_with_upstream: runs-on: ubuntu-latest name: Sync HEAD with upstream latest steps: # Step 1: run a standard checkout action, provided by github - name: Checkout HEAD uses: actions/checkout@v2 with: ref: main # Step 2: run this sync action - specify the upstream repo, upstream branch to sync with, and target sync branch - name: Pull upstream changes id: sync uses: bdougie/Fork-Sync-With-Upstream-action@fork with: upstream_repository: open-sauced/goals-template upstream_branch: main target_branch: main # optional github_token: ${{ secrets.GITHUB_TOKEN }} # optional, for accessing repos that require authentication # Step 3: Print a helpful timestamp for your records (optional) - name: Timestamp run: date