S/com/venndeta#2352
Conversation
matrix:
node_version: ['18.x', '20.x']
os: [ubuntu-latest, windows-latest, macOS-latest]
steps:
- uses: actions/checkout@v4
- name: Use Node.js ${{ matrix.node_version }}
uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node_version }}
- name: npm install, build and test
run: |
npm install
npm run build --if-present
npm test
Welcome to GitGitGadgetHi @DarkSecretMachineDDoSdrilllogpermerror, and welcome to GitGitGadget, the GitHub App to send patch series to the Git mailing list from GitHub Pull Requests. Please make sure that either:
You can CC potential reviewers by adding a footer to the PR description with the following syntax: NOTE: DO NOT copy/paste your CC list from a previous GGG PR's description, Also, it is a good idea to review the commit messages one last time, as the Git project expects them in a quite specific form:
It is in general a good idea to await the automated test ("Checks") in this Pull Request before contributing the patches, e.g. to avoid trivial issues such as unportable code. Contributing the patchesBefore you can contribute the patches, your GitHub username needs to be added to the list of permitted users. Any already-permitted user can do that, by adding a comment to your PR of the form Both the person who commented An alternative is the channel Once on the list of permitted usernames, you can contribute the patches to the Git mailing list by adding a PR comment If you want to see what email(s) would be sent for a After you submit, GitGitGadget will respond with another comment that contains the link to the cover letter mail in the Git mailing list archive. Please make sure to monitor the discussion in that thread and to address comments and suggestions (while the comments and suggestions will be mirrored into the PR by GitGitGadget, you will still want to reply via mail). If you do not want to subscribe to the Git mailing list just to be able to respond to a mail, you can download the mbox from the Git mailing list archive (click the curl -g --user "<EMailAddress>:<Password>" \
--url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txtTo iterate on your change, i.e. send a revised patch or patch series, you will first want to (force-)push to the same branch. You probably also want to modify your Pull Request description (or title). It is a good idea to summarize the revision by adding something like this to the cover letter (read: by editing the first comment on the PR, i.e. the PR description): To send a new iteration, just add another PR comment with the contents: Need help?New contributors who want advice are encouraged to join git-mentoring@googlegroups.com, where volunteers who regularly contribute to Git are willing to answer newbie questions, give advice, or otherwise provide mentoring to interested contributors. You must join in order to post or view messages, but anyone can join. You may also be able to find help in real time in the developer IRC channel, |
|
The pull request has 36 commits. The max allowed is 30. Please split the patch series into multiple pull requests. Also consider squashing related commits. |
| runs-on: windows-latest # For Linux, use ubuntu-latest | ||
| environment: dev | ||
| steps: | ||
| - name: 'Checkout GitHub Action' | ||
| uses: actions/checkout@v4 | ||
|
|
||
| # If you want to use Azure RBAC instead of Publish Profile, then uncomment the task below | ||
| # - name: 'Login via Azure CLI' | ||
| # uses: azure/login@v1 | ||
| # with: | ||
| # creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} # set up AZURE_RBAC_CREDENTIALS secrets in your repository | ||
|
|
||
| - name: Setup Node ${{ env.NODE_VERSION }} Environment | ||
| uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: ${{ env.NODE_VERSION }} | ||
|
|
||
| - name: 'Resolve Project Dependencies Using Npm' | ||
| shell: pwsh # For Linux, use bash | ||
| run: | | ||
| pushd './${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}' | ||
| npm install | ||
| npm run build --if-present | ||
| npm run test --if-present | ||
| popd | ||
|
|
||
| - name: 'Run Azure Functions Action' | ||
| uses: Azure/functions-action@v1 | ||
| id: fa | ||
| with: | ||
| app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }} | ||
| package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }} | ||
| publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }} # Remove publish-profile to use Azure RBAC |
| runs-on: windows-latest # For Linux, use ubuntu-latest | ||
| environment: dev | ||
| steps: | ||
| - name: 'Checkout GitHub Action' | ||
| uses: actions/checkout@v4 | ||
|
|
||
| # If you want to use Azure RBAC instead of Publish Profile, then uncomment the task below | ||
| # - name: 'Login via Azure CLI' | ||
| # uses: azure/login@v1 | ||
| # with: | ||
| # creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} # set up AZURE_RBAC_CREDENTIALS secrets in your repository | ||
|
|
||
| - name: 'Run Azure Functions Action' | ||
| uses: Azure/functions-action@v1 | ||
| id: fa | ||
| with: | ||
| app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }} | ||
| package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }} | ||
| publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }} # Remove publish-profile to use Azure RBAC |
| runs-on: ubuntu-latest | ||
| environment: dev | ||
| steps: | ||
| - name: 'Checkout GitHub Action' | ||
| uses: actions/checkout@v4 | ||
|
|
||
| # If you want to use Azure RBAC instead of Publish Profile, then uncomment the task below | ||
| # - name: 'Login via Azure CLI' | ||
| # uses: azure/login@v1 | ||
| # with: | ||
| # creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} # set up AZURE_RBAC_CREDENTIALS secrets in your repository | ||
|
|
||
| - name: Setup Python ${{ env.PYTHON_VERSION }} Environment | ||
| uses: actions/setup-python@v4 | ||
| with: | ||
| python-version: ${{ env.PYTHON_VERSION }} | ||
|
|
||
| - name: 'Resolve Project Dependencies Using Pip' | ||
| shell: bash | ||
| run: | | ||
| pushd './${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}' | ||
| python -m pip install --upgrade pip | ||
| pip install -r requirements.txt --target=".python_packages/lib/site-packages" | ||
| popd | ||
|
|
||
| - name: 'Run Azure Functions Action' | ||
| uses: Azure/functions-action@v1 | ||
| id: fa | ||
| with: | ||
| app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }} | ||
| package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }} | ||
| publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }} # Remove publish-profile to use Azure RBAC | ||
| scm-do-build-during-deployment: true | ||
| enable-oryx-build: true |
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: configure | ||
| run: ./configure | ||
| - name: make | ||
| run: make | ||
| - name: make check | ||
| run: make check | ||
| - name: make distcheck | ||
| run: make distcheck |
| runs-on: ${{ matrix.os }} | ||
|
|
||
| strategy: | ||
| # Set fail-fast to false to ensure that feedback is delivered for all matrix combinations. Consider changing this to true when your workflow is stable. | ||
| fail-fast: false | ||
|
|
||
| # Set up a matrix to run the following 3 configurations: | ||
| # 1. <Windows, Release, latest MSVC compiler toolchain on the default runner image, default generator> | ||
| # 2. <Linux, Release, latest GCC compiler toolchain on the default runner image, default generator> | ||
| # 3. <Linux, Release, latest Clang compiler toolchain on the default runner image, default generator> | ||
| # | ||
| # To add more build types (Release, Debug, RelWithDebInfo, etc.) customize the build_type list. | ||
| matrix: | ||
| os: [ubuntu-latest, windows-latest] | ||
| build_type: [Release] | ||
| c_compiler: [gcc, clang, cl] | ||
| include: | ||
| - os: windows-latest | ||
| c_compiler: cl | ||
| cpp_compiler: cl | ||
| - os: ubuntu-latest | ||
| c_compiler: gcc | ||
| cpp_compiler: g++ | ||
| - os: ubuntu-latest | ||
| c_compiler: clang | ||
| cpp_compiler: clang++ | ||
| exclude: | ||
| - os: windows-latest | ||
| c_compiler: gcc | ||
| - os: windows-latest | ||
| c_compiler: clang | ||
| - os: ubuntu-latest | ||
| c_compiler: cl | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v4 | ||
|
|
||
| - name: Set reusable strings | ||
| # Turn repeated input strings (such as the build output directory) into step outputs. These step outputs can be used throughout the workflow file. | ||
| id: strings | ||
| shell: bash | ||
| run: | | ||
| echo "build-output-dir=${{ github.workspace }}/build" >> "$GITHUB_OUTPUT" | ||
|
|
||
| - name: Configure CMake | ||
| # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make. | ||
| # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type | ||
| run: > | ||
| cmake -B ${{ steps.strings.outputs.build-output-dir }} | ||
| -DCMAKE_CXX_COMPILER=${{ matrix.cpp_compiler }} | ||
| -DCMAKE_C_COMPILER=${{ matrix.c_compiler }} | ||
| -DCMAKE_BUILD_TYPE=${{ matrix.build_type }} | ||
| -S ${{ github.workspace }} | ||
|
|
||
| - name: Build | ||
| # Build your program with the given configuration. Note that --config is needed because the default Windows generator is a multi-config generator (Visual Studio generator). | ||
| run: cmake --build ${{ steps.strings.outputs.build-output-dir }} --config ${{ matrix.build_type }} | ||
|
|
||
| - name: Test | ||
| working-directory: ${{ steps.strings.outputs.build-output-dir }} | ||
| # Execute tests defined by the CMake configuration. Note that --build-config is needed because the default Windows generator is a multi-config generator (Visual Studio generator). | ||
| # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail | ||
| run: ctest --build-config ${{ matrix.build_type }} |
| runs-on: ubuntu-latest | ||
| outputs: | ||
| digests: ${{ steps.hash.outputs.digests }} | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v4 | ||
|
|
||
| # ======================================================== | ||
| # | ||
| # Step 1: Build your artifacts. | ||
| # | ||
| # ======================================================== | ||
| - name: Build artifacts | ||
| run: | | ||
| # These are some amazing artifacts. | ||
| echo "artifact1" > artifact1 | ||
| echo "artifact2" > artifact2 | ||
| # ======================================================== | ||
| # | ||
| # Step 2: Add a step to generate the provenance subjects | ||
| # as shown below. Update the sha256 sum arguments | ||
| # to include all binaries that you generate | ||
| # provenance for. | ||
| # | ||
| # ======================================================== | ||
| - name: Generate subject for provenance | ||
| id: hash | ||
| run: | | ||
| set -euo pipefail | ||
| # List the artifacts the provenance will refer to. | ||
| files=$(ls artifact*) | ||
| # Generate the subjects (base64 encoded). | ||
| echo "hashes=$(sha256sum $files | base64 -w0)" >> "${GITHUB_OUTPUT}" | ||
| provenance: |
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v4 | ||
|
|
||
| - name: configure | ||
| run: ./configure | ||
|
|
||
| - name: Install dependencies | ||
| run: make | ||
|
|
||
| - name: Run check | ||
| run: make check | ||
|
|
||
| - name: Run distcheck | ||
| run: make distcheck |
| runs-on: ubuntu-latest | ||
|
|
||
| # Steps represent a sequence of tasks that will be executed as part of the job | ||
| steps: | ||
| # Runs a single command using the runners shell | ||
| - name: Send greeting | ||
| run: echo "Hello ${{ inputs.name }}" |
| runs-on: ubuntu-latest | ||
| strategy: | ||
| max-parallel: 5 | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: Set up Python 3.10 | ||
| uses: actions/setup-python@v3 | ||
| with: | ||
| python-version: '3.10' | ||
| - name: Add conda to system path | ||
| run: | | ||
| # $CONDA is an environment variable pointing to the root of the miniconda directory | ||
| echo $CONDA/bin >> $GITHUB_PATH | ||
| - name: Install dependencies | ||
| run: | | ||
| conda env update --file environment.yml --name base | ||
| - name: Lint with flake8 | ||
| run: | | ||
| conda install flake8 | ||
| # stop the build if there are Python syntax errors or undefined names | ||
| flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics | ||
| # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide | ||
| flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics | ||
| - name: Test with pytest | ||
| run: | | ||
| conda install pytest | ||
| pytest |
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - name: Build | ||
| run: cargo build --verbose | ||
| - name: Run tests | ||
| run: cargo test --verbose |
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
Thanks for taking the time to contribute to Git! Please be advised that the
Git community does not use github.com for their contributions. Instead, we use
a mailing list (git@vger.kernel.org) for code submissions, code reviews, and
bug reports. Nevertheless, you can use GitGitGadget (https://gitgitgadget.github.io/)
to conveniently send your Pull Requests commits to our mailing list.
For a single-commit pull request, please leave the pull request description
empty: your commit message itself should describe your changes.
Please read the "guidelines for contributing" linked above!