Searched +full:github +full:- +full:automation (Results 1 – 11 of 11) sorted by relevance
/llvm-project/.github/workflows/ |
H A D | merged-prs.yml | 9 # See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ 12 - closed 16 runs-on: ubuntu-latest 18 pull-requests: write 19 if: >- 20 (github.repository == 'llvm/llvm-project') && 21 (github.event.pull_request.merged == true) 23 - name: Checkout Automation Script 26 sparse-checkout: llvm/utils/git/ 29 - name: Setup Automation Script [all …]
|
H A D | issue-subscriber.yml | 6 - labeled 12 auto-subscribe: 13 runs-on: ubuntu-latest 14 if: github.repository == 'llvm/llvm-project' 16 - name: Checkout Automation Script 19 sparse-checkout: llvm/utils/git/ 22 - name: Setup Automation Script 23 working-directory: ./llvm/utils/git/ 25 pip install --require-hashes -r requirements.txt 27 - name: Update watchers [all …]
|
H A D | new-prs.yml | 9 # See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ 12 - opened 13 - reopened 14 - ready_for_review 15 - synchronize 19 runs-on: ubuntu-latest 21 pull-requests: write 23 # new to LLVM or to GitHub as a whole. Ideally we'd look for FIRST_TIMER 26 …# See https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=opened#pull_reque… 28 if: >- [all …]
|
H A D | pr-subscriber.yml | 6 - labeled 12 auto-subscribe: 13 runs-on: ubuntu-latest 14 if: github.repository == 'llvm/llvm-project' 16 - name: Checkout Automation Script 19 sparse-checkout: llvm/utils/git/ 22 - name: Setup Automation Script 23 working-directory: ./llvm/utils/git/ 25 pip install --require-hashes -r requirements.txt 27 - name: Update watchers [all …]
|
H A D | pr-request-release-note.yml | 9 - closed 12 request-release-note: 13 if: >- 14 github.repository_owner == 'llvm' && 15 startsWith(github.ref, 'refs/heads/release') 17 runs-on: ubuntu-latest 21 - name: Checkout Scripts 24 sparse-checkout: | 26 llvm/utils/git/github-automation.py 27 sparse-checkout-cone-mode: false [all …]
|
H A D | issue-release-workflow.yml | 4 # /cherry-pick <commit> <...> 6 # This comment will attempt to cherry-pick the given commits to the latest 8 # on github. 23 - created 24 - edited 27 - opened 30 …COMMENT_BODY: ${{ github.event.action == 'opened' && github.event.issue.body || github.event.comme… 33 backport-commits: 35 runs-on: ubuntu-latest 38 pull-requests: write [all …]
|
/llvm-project/llvm/utils/git/ |
H A D | github-automation.py | 3 # ======- github-automation - LLVM GitHub Automation Routines--*- pytho [all...] |
/llvm-project/polly/lib/External/isl/imath/ |
H A D | ChangeLog | 10 Added recursive multiplication and squaring (Karatsuba-Ofman) for 20 to be computed for > 30 digits or so. Added a pi-computation test 25 Cleaned up a sign-related bug in mp_int_gcd(), which would cause 47 Fixed a sign-related bug in mp_int_invmod(). 50 of 32-bit digits. Many architectures cannot shift by 32 bits at a 55 Fixed several arithmetic issues with 32-bit digits that arose due 56 to missing type-casts on the right-hand sides of assignments. 88 Silenced a sign-related warning in pi.c (related to printf). 91 original bug proof-of-concept from Tom Wu, and a series of new 107 returned is always the least non-negative member of the congruence [all …]
|
/llvm-project/llvm/docs/ |
H A D | MyFirstTypoFix.rst | 26 - know how to use an editor, 28 - have basic C++ knowledge, 30 - know how to install software on your system, 32 - are comfortable with the command line, 34 - have basic knowledge of git. 38 ----- [all...] |
H A D | CodingStandards.rst | 14 particularly important for large-scale code bases that follow a library-based 35 want patches that do large-scale reformatting of existing code. On the other 48 environment restrictions, historical restrictions, or due to third-party source 53 For automation, build-systems and utility scripts Python is preferred and 57 ---- [all...] |
/llvm-project/llvm/docs/TableGen/ |
H A D | index.rst | 19 domain-specific information. Because there may be a large number of these 26 hands the result off to a domain-specific `backend`_ for processing. See 27 the :doc:`TableGen Programmer's Reference <./ProgRef>` for an in-depth 28 description of TableGen. See :doc:`tblgen - Description to C++ Code 29 <../CommandGuide/tblgen>` for details on the ``*-tblgen`` commands 32 The current major users of TableGen are :doc:`The LLVM Target-Independent 34 <https://clang.llvm.org/docs/UsersManual.html#controlling-errors-and-warnings>`_. 47 TableGen files are interpreted by the TableGen program: `llvm-tblgen` available 52 ---------------- 55 specifies the file to read. If a filename is not specified, ``llvm-tblgen`` [all …]
|