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: actions/upload-artifact
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.2.2
Choose a base ref
...
head repository: actions/upload-artifact
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: ee69f02b3dfdecd58bb31b4d133da38ba6fe3700
Choose a head ref
  • 8 commits
  • 8 files changed
  • 4 contributors

Commits on Jan 5, 2021

  1. Update where does the upload go section (#162)

    @konradpabjan
    konradpabjan authored Jan 5, 2021
    Configuration menu
    Copy the full SHA
    16b8b2b View commit details
    Browse the repository at this point in the history

Commits on Jan 7, 2021

  1. Update README.md

    @konradpabjan
    konradpabjan authored Jan 7, 2021
    Configuration menu
    Copy the full SHA
    a4f98af View commit details
    Browse the repository at this point in the history

Commits on Jan 15, 2021

  1. Add on: pull_request trigger to CodeQL workflow (#165) 

    From February 2021, in order to provide feedback on pull requests, Code Scanning workflows must be configured with both `push` and `pull_request` triggers. This is because Code Scanning compares the results from a pull request against the results for the base branch to tell you only what has changed between the two.

Early in the beta period we supported displaying results on pull requests for workflows with only `push` triggers, but have discontinued support as this proved to be less robust.

See https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#scanning-pull-requests for more information on how best to configure your Code Scanning workflows.
    @rneatherway
    rneatherway authored Jan 15, 2021
    Configuration menu
    Copy the full SHA
    a1af2e8 View commit details
    Browse the repository at this point in the history

Commits on Feb 8, 2021

  1. Display a warning if user tries to upload over 10000 files

    @yacaovsnc
    yacaovsnc committed Feb 8, 2021
    Configuration menu
    Copy the full SHA
    0fbc4b7 View commit details
    Browse the repository at this point in the history

  2. update index.js

    @yacaovsnc
    yacaovsnc committed Feb 8, 2021
    Configuration menu
    Copy the full SHA
    e95d1b9 View commit details
    Browse the repository at this point in the history

  3. Merge pull request #173 from yacaovsnc/main 

    Display a warning if user tries to upload over 10000 files
    @yacaovsnc
    yacaovsnc authored Feb 8, 2021
    Configuration menu
    Copy the full SHA
    ea3d524 View commit details
    Browse the repository at this point in the history

Commits on Apr 6, 2021

  1. Bump y18n from 4.0.0 to 4.0.1 (#186) 

    Bumps [y18n](https://github.com/yargs/y18n) from 4.0.0 to 4.0.1.
- [Release notes](https://github.com/yargs/y18n/releases)
- [Changelog](https://github.com/yargs/y18n/blob/master/CHANGELOG.md)
- [Commits](https://github.com/yargs/y18n/commits)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
    @dependabot
    dependabot[bot] authored Apr 6, 2021
    Configuration menu
    Copy the full SHA
    bcd44ad View commit details
    Browse the repository at this point in the history

  2. Bump @actions/artifact to version 0.5.1 (#189) 

    * Bump @actions/artifact to version 0.5.1

* Update license versions
    @konradpabjan
    konradpabjan authored Apr 6, 2021
    Configuration menu
    Copy the full SHA
    ee69f02 View commit details
    Browse the repository at this point in the history
Loading