chore(.github): accept v3 bug reports, add triage dropdowns, wire up auto-labelers (#5754)

* chore(.github): accept v3 bug reports, add triage dropdowns, refresh templates

- bug_report.yml: remove the 'no v3 bug reports' banner (v3 bug reports
  are accepted), add required 'Wails version family' (v3/v2) and
  'Operating System' dropdowns, ask for wails3 doctor output (wails
  doctor for v2), fix v2-era links and mark the v2 binding tests
  reference as v2-specific alongside the v3 generator path
- feature_request.yml: replace the stale Wails v1 notice with the
  discussion-first note (Discord / GitHub Discussions), matching
  CONTRIBUTING.md
- documentation.yml: point the contribution guidelines link at
  https://v3.wails.io/contributing/
- config.yml: disable blank issues, align the Discord invite with
  CONTRIBUTING.md
- file-labeler.yml: convert to the actions/labeler v5 configuration
  format
- delete legacy Probot .github/stale.yml (superseded by
  workflows/stale-issues.yml using actions/stale@v9)
- add CODE_OF_CONDUCT.md (Contributor Covenant v2.1)

* ci: wire up issue and PR auto-labelers

Consumes the previously orphaned .github/issue-labeler.yml
(github/issue-labeler@v3.4, non-versioned regex format) and
.github/file-labeler.yml (actions/labeler@v5) configs.

* docs: point enhancement guidance at the WEP process

The Wails Enhancement Proposal process (v3/wep) was not referenced
anywhere contributors actually look. Reference it from the feature
request template, CONTRIBUTING.md and the v3 docs site (contributing
page gets a step-by-step summary, feedback page a pointer).

Also fixes the stale feedback-guide link in CONTRIBUTING.md
(/getting-started/feedback/ -> /feedback/).

* chore: align Code of Conduct contact with the published site CoC

The v2 website has published a Contributor Covenant CoC at
wails.io/coc with coc@wails.io as the enforcement contact; use the
same address in the repo-level file.

* docs: make GitHub Discussions the official venue for WEP discussion

Proposals are discussed in the Enhancement Proposals category on
GitHub Discussions. Discord remains available for informal chat but
is no longer the primary venue. Adds an explicit discuss-first step
to the WEP README's Idea Initiation section.

* docs(wep): add index, statuses, numbering and platform section to the WEP process

Implements the process improvements agreed with the maintainer:

- WEP Index table in the README (number, title, status, discussion,
  implementation) with documented status values
- Metadata header in the template (number, status, discussion link,
  implementor) and a Platform Considerations section
- 'Do I Need a WEP?' section defining when a proposal is required
- Support is now measured by upvotes on the Enhancement Proposals
  discussion rather than thumbs-ups on a draft PR
- Decisions recorded in a standard comment format; rejected proposals
  stay findable via the index
- Accepted proposals not started within 3 months become up for grabs
- Migrated the existing proposal as WEP 0001 (dir renamed to
  0001-titlebar-buttons, header added, status Implemented via #3508)

* docs(wep): the WEP PR is the single discussion venue

Per maintainer decision: proposals are discussed on the WEP PR itself
(comments for feedback, thumbs-up reactions for support), not in a
separate discussion thread. Pre-proposal ideas can optionally be
floated in the Ideas category on GitHub Discussions or on Discord.
Index column Discussion renamed to Proposal.

---------

Co-authored-by: taliesin-ai <lea.anthony@gmail.com>

Author: taliesin-ai

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -7,25 +7,46 @@ body:
   - type: markdown
     attributes:
       value: |
-        ***Please note: No bug reports are currently being accepted for Wails v3***
-        ***Please note: No bug reports are currently being accepted for Wails v3***
-        ***Please note: No bug reports are currently being accepted for Wails v3***
         Before submitting this issue, please do the following:
         - Do a web search for your error. This usually leads to a much better understanding of the issue.
-        - Prove that the error is indeed a Wails bug and not an application bug, with a specific set of steps to reproduce. 
+        - Prove that the error is indeed a Wails bug and not an application bug, with a specific set of steps to reproduce.
         - Search the issue tracker using [this link](https://github.com/wailsapp/wails/issues?q=is%3Aissue+).
         - Search the [discussion forums](https://github.com/wailsapp/wails/discussions?discussions_q=type+your+issue+here).
-        - Read the [Troubleshooting Guide](https://wails.io/docs/next/guides/troubleshooting).
+        - For v3, check the [FAQ](https://v3.wails.io/faq/) and the [feedback guide](https://v3.wails.io/feedback/). For v2, read the [Troubleshooting Guide](https://wails.io/docs/guides/troubleshooting).
         - Create a [Minimal Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example) and link to it in the issue.
-        - If your issue is related to TypeScript generation, please open a ticket and create a PR with a failing test case.
-        TS tests can be found [here](https://github.com/wailsapp/wails/tree/master/v2/internal/binding/binding_test). Remember to add
-        your test to the `binding_test.go` file.
-        - Try to fix it yourself. Keep a list of things you have done to fix the problem.   
+        - If your issue is related to the bindings or TypeScript generation, please open a ticket and create a PR with a failing test case.
+          For v3, the binding generator tests live [here](https://github.com/wailsapp/wails/tree/master/v3/internal/generator).
+          For v2 only, TS tests can be found [here](https://github.com/wailsapp/wails/tree/master/v2/internal/binding/binding_test). Remember to add your test to the `binding_test.go` file.
+        - Try to fix it yourself. Keep a list of things you have done to fix the problem.
 
         If after doing all the above, the problem remains, please continue with this ticket providing *all* the information requested.
 
         Bug reports that do not follow these steps will likely be closed, so please help us to help you.
 
+  - type: dropdown
+    id: version_family
+    attributes:
+      label: Wails version family
+      description: Which major version of Wails are you using?
+      options:
+        - v3
+        - v2
+    validations:
+      required: true
+  - type: dropdown
+    id: operating-system
+    attributes:
+      label: Operating System
+      description: Which operating system does the bug occur on?
+      options:
+        - Windows
+        - macOS
+        - Linux
+        - iOS (experimental)
+        - Android (experimental)
+        - Multiple / Other
+    validations:
+      required: true
   - type: textarea
     id: description
     attributes:
@@ -75,7 +96,7 @@ body:
     id: systemdetails
     attributes:
       label: System Details
-      description: Please add the output of `wails doctor`.
+      description: Please add the output of `wails3 doctor` (for v2 projects, use `wails doctor`).
       render: shell
     validations:
       required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
-blank_issues_enabled: true
+blank_issues_enabled: false
 contact_links:
   - name: Discord Chat
-    url: https://discord.gg/BrRSWTaxVK
+    url: https://discord.gg/JDdSxwjhGf
     about: Ask questions and discuss with other Wails users in real time.
 
   - name: GitHub Community Discussions

.github/ISSUE_TEMPLATE/documentation.yml

@@ -20,7 +20,7 @@ body:
     attributes:
       label: Have you read the Documentation Contribution Guidelines?
       options:
-        - label: I have read the [Documentation Contribution Guidelines](https://wails.io/community-guide#ways-of-contributing).
+        - label: I have read the [Documentation Contribution Guidelines](https://v3.wails.io/contributing/).
           required: true
 
   - type: textarea

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -8,7 +8,7 @@ body:
     attributes:
       value: |
         Before opening a feature request, please check the [Roadmap](https://github.com/wailsapp/wails/discussions/1484) to see if it has already been requested.
-        ***Please note: No new feature requests are being accepted for Wails v1***
+        ***Please note: Enhancements should be discussed in [Ideas](https://github.com/wailsapp/wails/discussions/categories/ideas) on GitHub Discussions or on [Discord](https://discord.gg/JDdSxwjhGf) before opening a feature request. Substantial new functionality should be submitted as a [Wails Enhancement Proposal (WEP)](https://github.com/wailsapp/wails/blob/master/v3/wep/README.md). See the [feedback guide](https://v3.wails.io/feedback/) for details.***
 
   - type: textarea
     attributes:

.github/file-labeler.yml

@@ -1,44 +1,63 @@
-# File path specific labels
+# File path specific labels (actions/labeler v5 configuration format)
 v2-only:
-  - 'v2/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - 'v2/**/*'
 
 v3-alpha:
-  - 'v3/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - 'v3/**/*'
 
 windows:
-  - '**/*_windows.go'
-  - 'v2/internal/frontend/desktop/windows/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - '**/*_windows.go'
+          - 'v2/internal/frontend/desktop/windows/**/*'
 
 macos:
-  - '**/*_darwin.go'
-  - 'v2/internal/frontend/desktop/darwin/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - '**/*_darwin.go'
+          - 'v2/internal/frontend/desktop/darwin/**/*'
 
 linux:
-  - '**/*_linux.go'
-  - 'v2/internal/frontend/desktop/linux/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - '**/*_linux.go'
+          - 'v2/internal/frontend/desktop/linux/**/*'
 
 cli:
-  - 'v2/cmd/**/*'
-  - 'v3/cmd/**/*'
-  - '**/cli/**/*'
-  - '**/commands/**/*'
-  
+  - changed-files:
+      - any-glob-to-any-file:
+          - 'v2/cmd/**/*'
+          - 'v3/cmd/**/*'
+          - '**/cli/**/*'
+          - '**/commands/**/*'
+
 documentation:
-  - '**/*.md'
-  - 'docs/**/*'
-  - 'website/**/*'
-  - 'mkdocs-website/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - '**/*.md'
+          - 'docs/**/*'
+          - 'website/**/*'
+          - 'mkdocs-website/**/*'
 
 templates:
-  - '**/templates/**/*'
-  - '**/template/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - '**/templates/**/*'
+          - '**/template/**/*'
 
 runtime:
-  - '**/runtime/**/*'
-  - 'v2/internal/runtime/**/*'
-  - 'v3/internal/runtime/**/*'
-  
-bindings:
-  - 'v2/internal/binding/**/*'
-  - 'v3/internal/generator/**/*'
+  - changed-files:
+      - any-glob-to-any-file:
+          - '**/runtime/**/*'
+          - 'v2/internal/runtime/**/*'
+          - 'v3/internal/runtime/**/*'
 
+bindings:
+  - changed-files:
+      - any-glob-to-any-file:
+          - 'v2/internal/binding/**/*'
+          - 'v3/internal/generator/**/*'

.github/stale.yml

@@ -0,0 +1,36 @@
+name: Auto Labeler
+
+on:
+  issues:
+    types: [opened, edited]
+  pull_request_target:
+
+jobs:
+  issue-labeler:
+    name: Label issues
+    if: github.event_name == 'issues'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+    steps:
+      - uses: github/issue-labeler@v3.4
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          configuration-path: .github/issue-labeler.yml
+          enable-versioned-regex: 0
+          include-title: 1
+
+  pr-labeler:
+    name: Label pull requests
+    if: github.event_name == 'pull_request_target'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+    steps:
+      - uses: actions/labeler@v5
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          configuration-path: .github/file-labeler.yml
+          sync-labels: false

.github/workflows/labeler.yml

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances
+  of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+coc@wails.io.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CODE_OF_CONDUCT.md

@@ -15,7 +15,7 @@ Thanks for your interest in contributing! Wails has two active tracks. Pick the
 - Docs: [v3.wails.io](https://v3.wails.io/).
 - Detailed contributor guide: [v3.wails.io/contributing](https://v3.wails.io/contributing/).
 - Changelog: v3 entries are added automatically from your PR on merge. To control the wording, add your own entry to `v3/UNRELEASED_CHANGELOG.md` and the automation will use it instead.
-- **Enhancements require prior discussion** on [Discord](https://discord.gg/JDdSxwjhGf) — see the [feedback guide](https://v3.wails.io/getting-started/feedback/).
+- **Enhancements require prior discussion** in [Ideas](https://github.com/wailsapp/wails/discussions/categories/ideas) on GitHub Discussions (see the [feedback guide](https://v3.wails.io/feedback/)). Substantial new functionality goes through the [Wails Enhancement Proposal (WEP) process](v3/wep/README.md).
 
 ## Pull request checklist