Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: google-github-actions/.github
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1
Choose a base ref
...
head repository: google-github-actions/.github
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
  • 14 commits
  • 8 files changed
  • 3 contributors

Commits on Jan 31, 2025

  1. Update release process (1/n) (#38)

    @sethvargo
    sethvargo authored Jan 31, 2025
    Configuration menu
    Copy the full SHA
    d221528 View commit details
    Browse the repository at this point in the history

  2. Test new release process (1/n)

    @sethvargo
    sethvargo committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    aa70d1b View commit details
    Browse the repository at this point in the history

  3. Test new release process (2/n)

    @sethvargo
    sethvargo committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    d52cac7 View commit details
    Browse the repository at this point in the history

  4. Pull from branch for now

    @sethvargo
    sethvargo committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    e723c03 View commit details
    Browse the repository at this point in the history

  5. Revert back to main

    @sethvargo
    sethvargo committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    ca92f51 View commit details
    Browse the repository at this point in the history

  6. Try new actual release process

    @sethvargo
    sethvargo committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    919b586 View commit details
    Browse the repository at this point in the history

Commits on Apr 25, 2025

  1. Update workflow references (#39)

    @sethvargo
    sethvargo authored Apr 25, 2025
    Configuration menu
    Copy the full SHA
    a3df4ec View commit details
    Browse the repository at this point in the history

Commits on Jul 17, 2025

  1. Add YAMLint YAML (#40)

    @sethvargo
    sethvargo authored Jul 17, 2025
    Configuration menu
    Copy the full SHA
    ff59587 View commit details
    Browse the repository at this point in the history

Commits on Jul 18, 2025

  1. Add global linters (#41) 

    Do not merge
    @sethvargo
    sethvargo authored Jul 18, 2025
    Configuration menu
    Copy the full SHA
    2f48f3b View commit details
    Browse the repository at this point in the history

  2. Set permissions on workflows (#42)

    @sethvargo
    sethvargo authored Jul 18, 2025
    Configuration menu
    Copy the full SHA
    525ebd3 View commit details
    Browse the repository at this point in the history

Commits on Jul 31, 2025

  1. Check additional YAML file paths for ratchet (#43)

    @sethvargo
    sethvargo authored Jul 31, 2025
    Configuration menu
    Copy the full SHA
    145cb9a View commit details
    Browse the repository at this point in the history

Commits on Aug 28, 2025

  1. Also update floating tags on release (#44) 

    GitHub changed the immutable actions program, and it no longer computes
floating tags.
    @sethvargo
    sethvargo authored Aug 28, 2025
    Configuration menu
    Copy the full SHA
    29c6d38 View commit details
    Browse the repository at this point in the history

Commits on Sep 2, 2025

  1. Use Node 24 now (#45)

    @sethvargo
    sethvargo authored Sep 2, 2025
    Configuration menu
    Copy the full SHA
    76c7c9d View commit details
    Browse the repository at this point in the history

Commits on Apr 17, 2026

  1. Deploy centralized organization stale bot (#48) 

    <!--
Thank you for proposing a pull request! Please note that SOME TESTS WILL
LIKELY FAIL due to how GitHub exposes secrets in Pull Requests from
forks.
Someone from the team will review your Pull Request and respond.

Please describe your change and any implementation details below.
-->
- Deploy a centralized multi-repository stale bot utilizing GitHub's
official `actions/stale` within a dynamic matrix workflow.
 
- To prevent individual repositories from bypassing security standards,
enforce
Actionlint and Scorecard centrally using a GitHub Organization Ruleset.

---------

Signed-off-by: Chris <chris.ge@live.com>
Co-authored-by: Mike Verbanic <5046972+verbanicm@users.noreply.github.com>
    @ChrisGe4 @verbanicm
    ChrisGe4 and verbanicm authored Apr 17, 2026
    Configuration menu
    Copy the full SHA
    7596dc0 View commit details
    Browse the repository at this point in the history
Loading