mirror of
https://github.com/zed-industries/zed.git
synced 2025-01-30 22:34:13 +00:00
df20bae80e
This PR updates the regex we use to search for issues to not search for `#NNNN`, as it's not specific enough. It currently catches issue numbers from other repos, which are then linked to random Zed issues/PRs that happen to have the same number: <img width="935" alt="Screenshot 2024-08-15 at 3 50 29 PM" src="https://github.com/user-attachments/assets/b779e503-3027-43e2-b355-e81d8d094694"> As well as catching PRs: <img width="924" alt="Screenshot 2024-08-15 at 3 48 59 PM" src="https://github.com/user-attachments/assets/6c2f7594-9234-4454-97da-5a33a1844892"> Given that: 1. We can't distinguish any given `#NNNN` as an issue _and_ can't ensure it belongs to the Zed repo 2. Any issue/PR referenced as `#NNNN` will already create a backlink It seems that looking for these is causing more noise than signal. Release Notes: - N/A |
||
---|---|---|
.. | ||
danger | ||
eula | ||
flatpak | ||
lib | ||
licenses | ||
update_top_ranking_issues | ||
analyze_highlights.py | ||
bootstrap | ||
bump-extension-cli | ||
bump-nightly | ||
bump-zed-minor-versions | ||
bump-zed-patch-version | ||
bundle-linux | ||
bundle-mac | ||
check-licenses | ||
clear-target-dir-if-larger-than | ||
clippy | ||
collab-flamegraph | ||
crate-dep-graph | ||
create-migration | ||
deploy-collab | ||
deploy-postgrest | ||
draft-release-notes | ||
drop-test-dbs | ||
generate-eula-rtf | ||
generate-licenses | ||
get-changes-since | ||
get-crate-version | ||
get-preview-channel-changes | ||
get-released-version | ||
histogram | ||
import-themes | ||
install-linux | ||
install.sh | ||
kube-shell | ||
linux | ||
metal-debug | ||
prompts | ||
randomized-test-ci | ||
randomized-test-minimize | ||
reset_db | ||
run-local-minio | ||
seed-db | ||
squawk | ||
storybook | ||
symbolicate | ||
trigger-release | ||
upload-extension-cli | ||
upload-nightly | ||
what-is-deployed | ||
zed-local |