fix: point the discussion link at org discussions - #20
Merged
Conversation
This repository has Discussions disabled, so the contact link led to a 404. The heibench org has org-level Discussions enabled, hosted by heibench/.github, which is a real target.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.github/ISSUE_TEMPLATE/config.ymlsent people to this repository's Discussions tab, which is disabled — the link was a 404, and had been before the org move too.The heibench org now has org-level Discussions enabled (hosted by
heibench/.github), which is a real destination:https://github.com/heibench/gerberdiff/discussionshttps://github.com/orgs/heibench/discussionsKept as a contact link rather than deleted, so the route to asking a question still exists.
Alternative if preferred: enable Discussions on this repo and revert. Pointing at the org keeps one place for questions across all members, which seems the better default for a five-repo org.