Remove github issue template for git beta and improve related CI (#26707)
Remove the git beta issue template. Improve ci.yml `job_spec` so that changes like this will not require CI in the future. Improve ci.yml `job_spec` ensuring `output.run_license` exported for Cargo.lock. Release Notes: - N/A --------- Co-authored-by: Peter Tripp <peter@zed.dev>
This commit is contained in:
parent
2183fc674d
commit
b5a7fb13c3
2 changed files with 7 additions and 52 deletions
51
.github/ISSUE_TEMPLATE/0_git_beta_bug_report.yml
vendored
51
.github/ISSUE_TEMPLATE/0_git_beta_bug_report.yml
vendored
|
@ -1,51 +0,0 @@
|
||||||
name: Git Beta
|
|
||||||
description: There is a bug related to new Git features in Zed
|
|
||||||
type: "Bug"
|
|
||||||
labels: [git]
|
|
||||||
title: "Git Beta: <a short description of the Git bug>"
|
|
||||||
body:
|
|
||||||
- type: textarea
|
|
||||||
attributes:
|
|
||||||
label: Summary
|
|
||||||
description: Describe the bug with a one line summary, and provide detailed reproduction steps
|
|
||||||
value: |
|
|
||||||
<!-- Please insert a one line summary of the issue below -->
|
|
||||||
|
|
||||||
<!-- Include all steps necessary to reproduce from a clean Zed installation. Be verbose -->
|
|
||||||
Steps to trigger the problem:
|
|
||||||
1.
|
|
||||||
2.
|
|
||||||
3.
|
|
||||||
|
|
||||||
Actual Behavior:
|
|
||||||
|
|
||||||
Expected Behavior:
|
|
||||||
|
|
||||||
validations:
|
|
||||||
required: true
|
|
||||||
- type: textarea
|
|
||||||
id: environment
|
|
||||||
attributes:
|
|
||||||
label: Zed Version and System Specs
|
|
||||||
description: 'Open Zed, and in the command palette select "zed: Copy System Specs Into Clipboard"'
|
|
||||||
placeholder: |
|
|
||||||
Output of "zed: Copy System Specs Into Clipboard"
|
|
||||||
validations:
|
|
||||||
required: true
|
|
||||||
- type: textarea
|
|
||||||
attributes:
|
|
||||||
label: If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue.
|
|
||||||
description: |
|
|
||||||
macOS: `~/Library/Logs/Zed/Zed.log`
|
|
||||||
Linux: `~/.local/share/zed/logs/Zed.log` or $XDG_DATA_HOME
|
|
||||||
If you only need the most recent lines, you can run the `zed: open log` command palette action to see the last 1000.
|
|
||||||
value: |
|
|
||||||
<details><summary>Zed.log</summary>
|
|
||||||
|
|
||||||
<!-- Click below this line and paste or drag-and-drop your log-->
|
|
||||||
```
|
|
||||||
|
|
||||||
```
|
|
||||||
<!-- Click above this line and paste or drag-and-drop your log--></details>
|
|
||||||
validations:
|
|
||||||
required: false
|
|
8
.github/workflows/ci.yml
vendored
8
.github/workflows/ci.yml
vendored
|
@ -28,6 +28,7 @@ jobs:
|
||||||
if: github.repository_owner == 'zed-industries'
|
if: github.repository_owner == 'zed-industries'
|
||||||
outputs:
|
outputs:
|
||||||
run_tests: ${{ steps.filter.outputs.run_tests }}
|
run_tests: ${{ steps.filter.outputs.run_tests }}
|
||||||
|
run_license: ${{ steps.filter.outputs.run_license }}
|
||||||
runs-on:
|
runs-on:
|
||||||
- ubuntu-latest
|
- ubuntu-latest
|
||||||
steps:
|
steps:
|
||||||
|
@ -47,7 +48,12 @@ jobs:
|
||||||
git fetch origin "$GITHUB_BASE_REF" --depth=350
|
git fetch origin "$GITHUB_BASE_REF" --depth=350
|
||||||
COMPARE_REV=$(git merge-base "origin/${GITHUB_BASE_REF}" HEAD)
|
COMPARE_REV=$(git merge-base "origin/${GITHUB_BASE_REF}" HEAD)
|
||||||
fi
|
fi
|
||||||
if [[ $(git diff --name-only $COMPARE_REV ${{ github.sha }} | grep -v "^docs/") ]]; then
|
# Specify anything which should skip full CI in this regex:
|
||||||
|
# - docs/
|
||||||
|
# - .github/ISSUE_TEMPLATE/
|
||||||
|
# - .github/workflows/ (except .github/workflows/ci.yml)
|
||||||
|
SKIP_REGEX='^(docs/|\.github/(ISSUE_TEMPLATE|workflows/(?!ci)))'
|
||||||
|
if [[ $(git diff --name-only $COMPARE_REV ${{ github.sha }} | grep -vP "$SKIP_REGEX") ]]; then
|
||||||
echo "run_tests=true" >> $GITHUB_OUTPUT
|
echo "run_tests=true" >> $GITHUB_OUTPUT
|
||||||
else
|
else
|
||||||
echo "run_tests=false" >> $GITHUB_OUTPUT
|
echo "run_tests=false" >> $GITHUB_OUTPUT
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue