aboutsummaryrefslogtreecommitdiffstats
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* Use `set-env` instead of `grep` in each stepKazuhiro NISHIYAMA2019-08-281-15/+16
|
* Use JOBS again like macos.ymlKazuhiro NISHIYAMA2019-08-281-2/+6
|
* Change name to `Tests (test-bundled-gems)`Kazuhiro NISHIYAMA2019-08-281-1/+1
|
* Add name to autoconfKazuhiro NISHIYAMA2019-08-281-1/+2
|
* Remove GITHUB_SHA from jobs.<job_id>.steps.envKazuhiro NISHIYAMA2019-08-283-7/+0
| | | | | because default value overrides it. https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables
* Allow missing projectnumber [ci skip]Kazuhiro NISHIYAMA2019-08-281-1/+1
|
* Show projectnumber in current index.html and GITHUB_SHAKazuhiro NISHIYAMA2019-08-281-0/+2
|
* Fix doxygen actionKazuhiro NISHIYAMA2019-08-281-26/+10
| | | | | | | - Fix checkout error: `fatal: destination path '.' already exists and is not an empty directory.` - Remove `GITHUB_SHA` in env, because set automatically https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables - Change minute from 0 to 20 for test soon
* Run on schedule only and skip if not modifiedKazuhiro NISHIYAMA2019-08-281-17/+35
|
* Make doxygen / coverage torelant to clone raceTakashi Kokubun2019-08-282-4/+4
| | | | | | | | | | | a little. Doing both `git clone --depth=1` and `git reset --hard ${sha}` does not make sense (the latter command either does nothing or just fails), so I added non-1 value as a depth. Maybe we don't need depth=50 for pull_request and schedule, so it's 10 for now.
* Drop more unused configs from doxygen and coverageTakashi Kokubun2019-08-272-16/+0
| | | | workflows, because mame said he has never seen it.
* Omit unused matrix strategy from doxygen workflowTakashi Kokubun2019-08-271-4/+0
|
* Add graphviz for dot commandKazuhiro NISHIYAMA2019-08-271-1/+1
|
* Doxygen in GitHub Actions (#2406)Yusuke Endoh2019-08-271-0/+62
| | | * .github/workflows/doxygen.yml: add a workflow for doxygen in Actions
* Revert "Explain which test task"Nobuyoshi Nakada2019-08-272-4/+4
| | | | | | This reverts commit 9bc1667a188392b94971b9b96507af76cbd5f413. `name` lines are not expanded.
* .github/workflows/coverage.yml: add a cron job for coverage in ActionsYusuke Endoh2019-08-271-0/+68
|
* Explain which test taskNobuyoshi Nakada2019-08-272-4/+4
|
* Expand JOBS instead of meaningless export (#2402)Kazuhiro NISHIYAMA2019-08-261-7/+3
| | | | | | | | | * Expand JOBS instead of meaningless export * Remove -j option in TESTOPTS of test-bundled-gems https://github.com/ruby/ruby/runs/203129516#step:10:167 > invalid option: -j3
* Make GitHub Actions Slack notification consistentTakashi Kokubun2019-08-223-6/+12
| | | | | | | | | | | | | | | | | with Travis, rather than AppVeyor. Formerly it was made similar to AppVeyor to provide some normal set of CI failure notification. But for some reason people preferred a shorter variant and introduced a1d606c079f6c3d1779d885e0bf2e3991251609e and d8d8015b93c6daa8d8433895464db3493a2056e2. Instead of AppVeyor format, this commit chose Travis-like format to achieve consistency and to include usual CI-failure information, while keeping it one-liner for people who prefer short notifications. Note that this shrinks the 40-char sha to 10-char, using the new feature of k0kubun/action-slack@v2.0.0: https://github.com/k0kubun/action-slack/commit/1c88a05dac664cbafa1c99a37f292ed23ac1c289
* Remove footer from message to Slackaycabta2019-08-223-3/+0
|
* Show short message to Slackaycabta2019-08-223-12/+3
|
* Debug GitHub context on broken notificationTakashi Kokubun2019-08-211-0/+5
| | | | | | sometimes Slack notification footer becomes just " at ". It seems like `github.event.head_commit` is missing. Let me debug the context.
* Skip tests on Actions if [ci skip]Takashi Kokubun2019-08-203-4/+5
| | | | | It seems that we cannot easily apply job-level [ci skip]. Therefore this commit skips only Tests step if it's [ci skip].
* Reduce sub-shell and use `&&` instead of `;`Kazuhiro NISHIYAMA2019-08-191-1/+1
|
* Roughly retry `brew update`Takashi Kokubun2019-08-191-1/+1
| | | | as it failed randomly https://github.com/ruby/ruby/runs/196712109
* Stop reporting test-bundled-gems resultsTakashi Kokubun2019-08-192-0/+16
| | | | | | by marking continue-on-error. I dropped it to test Slack notification, and I finished to test it.
* Workaround errors on multi-line commit messageTakashi Kokubun2019-08-193-3/+9
| | | | by using toJson with fields.
* Make Slack notification availableTakashi Kokubun2019-08-194-71/+30
| | | | | | for macOS / Windows as well. Docker-based GitHub Action does not work on these OSes.
* Implement Slack notification for ActionsTakashi Kokubun2019-08-194-17/+85
|
* Revert "Try notifying Slack from Actions"Takashi Kokubun2019-08-183-36/+0
| | | | | | This reverts commit d8807e8b1a9d09ee1543e18618b4ef7e8203c616. We'd need more features. Reverting to customize this later.
* Try notifying Slack from ActionsTakashi Kokubun2019-08-183-0/+36
| | | | | https://github.com/8398a7/action-slack https://github.com/marketplace/actions/action-slack
* Drop continue-on-error for make checkTakashi Kokubun2019-08-181-2/+1
| | | | Like macos.yml, we don't need to ignore `make check` failure.
* Added missing condition for test-bundler and test-bundled-gems.Hiroshi SHIBATA2019-08-171-0/+1
|
* Added test check to ubuntu on GitHub ActionsHiroshi SHIBATA2019-08-171-1/+8
|
* Disable fail-fast of GitHub ActionsTakashi Kokubun2019-08-173-0/+3
| | | | | | | This is default: true https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast When `make check` fails, we do not want to cancel `make test-bundler`.
* Mark bundler / bundled-gems as continue-on-failureTakashi Kokubun2019-08-142-1/+12
| | | | | because these tests have failed too often and it's false-positive for checking healthiness of the master branch.
* Update the description of check_branchTakashi Kokubun2019-08-141-6/+7
|
* Rename check_branch.master to pull_request.check_branchTakashi Kokubun2019-08-141-2/+2
| | | | | | | | because it's shown as just "master" on a pull request which does not have the check_branch.master job yet. "check_branch" would be easier to understand and now we can grep it from master branch.
* Try to fix variable reference on Windows (#2361)Takashi Kokubun2019-08-141-8/+2
| | | https://github.com/ruby/ruby/runs/192869165
* Stop using official actions/checkoutTakashi Kokubun2019-08-143-12/+39
| | | | | | because it has been unstable, and also it sometimes does not work for a pull request like: https://github.com/ruby/ruby/pull/2358/checks?check_run_id=192685048#step:4:17
* Use the official actions/checkout again (#2357)Takashi Kokubun2019-08-133-6/+12
| | | | because clone does not checkout exact commit sha, and also we'd need to handle pull_request on fork, so I tentatively stopped to do this.
* Update the comment in check_branch [ci skip] (#2355)Takashi Kokubun2019-08-131-5/+3
|
* Explain the current status of branches [ci skip] (#2350)Takashi Kokubun2019-08-131-2/+9
|
* Update check_branch description a little [ci skip]Takashi Kokubun2019-08-131-0/+1
|
* Add a quick job to be used for branch protectionTakashi Kokubun2019-08-121-0/+15
|
* added --disable-install-doc to Windows workflow of GitHub ActionsHiroshi SHIBATA2019-08-121-1/+1
| | | | Closes: https://github.com/ruby/ruby/pull/2346
* Try to nmake testHiroshi SHIBATA2019-08-121-0/+5
|
* Try to merge windows 2016 and 2019Hiroshi SHIBATA2019-08-122-39/+13
|
* Added windows-2019 workflowHiroshi SHIBATA2019-08-121-0/+35
|
* Try to nmakeHiroshi SHIBATA2019-08-121-0/+6
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-25 11:43:57 +0000