Searched +full:- +full:- +full:branch +full:- +full:repo +full:- +full:token (Results 1 – 8 of 8) sorted by relevance
3 # ======- github-automation - LLVM GitHub Automation Routines--*- python -*--==#7 # SPDX-Licens362 def token(self) -> str: global() member in ReleaseWorkflow 394 def repo(self) -> github.Repository.Repository: global() member in ReleaseWorkflow [all...]
6 - "Check code formatting"7 - "Check for private emails used in PRs"8 - "PR Request Release Note"10 - completed16 pr-comment:17 runs-on: ubuntu-latest19 pull-requests: write27 - name: Fetch Sources30 sparse-checkou[all...]
2 # to the release branch using comments on issues.4 # /cherry-pick <commit> <...>6 # This comment will attempt to cherry-pick the given commits to the latest7 # release branch (release/Y.x) and if successful, push the result to a branch10 # /branch <owner>/<repo>/<branch>12 # This comment will create a pull request from <branch> to the latest release13 # branch.23 - created24 - edited27 - opened[all …]
9 - closed12 request-release-note:13 if: >-17 runs-on: ubuntu-latest19 # We need to pull the script from the main branch, so that we ensure21 - name: Checkout Scripts24 sparse-checkout: |26 llvm/utils/git/github-automation.py27 sparse-checkout-cone-mode: false29 - name: Install Dependencies[all …]
8 # code from the pull request branch.9 # See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/12 - opened13 - reopened14 - ready_for_review15 - synchronize19 runs-on: ubuntu-latest21 pull-requests: write26 …# See https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=opened#pull_reque…28 if: >-[all …]
8 This document contains information about successfully releasing LLVM ---9 including sub-projects: e.g., ``clang`` and ``compiler-rt`` --- to the public.21 LLVM is released on a time based schedule --[all...]
22 infrastructure) will continue to work with a Git-based LLVM.29 This proposal relates only to moving the hosting of our source-code repository31 using GitHub's issue tracker, pull-requests, or code-review.35 username/password-hash.41 ----------------57 --------66 through the Git-SVN integration.82 -----------85 projects. Any of these could replace the code-hosting infrastructure that we92 BitBucket: it offers read-write **SVN** access to the repository[all …]
1 # ===----------[all...]