JonKazama-Hellion
9a8a014795
Chat 2 has entered a major rework that Infi confirmed makes selective patches no longer portable. The cherry-pick pipeline as a routine workflow stops with the v1.4.x cycle. Documentation reflects the new state across all touchpoints. UPSTREAM_SYNC.md rewritten: replaces the "How I Cherry-Pick" / "Reviewing What Is New Upstream" / "Conflict Handling" sections with "Why Cherry-Picking Stopped", "What Closing the Pipeline Means in Practice", "What Does Not Change", "What Could Re-Open Later". Existing cherry-pick trails in the git history stay intact, EUPL-1.2 anchor lines and NOTICE.md remain canonical. README.md, CONTRIBUTING.md, ROADMAP.md, THIRD_PARTY_NOTICES.md and the PR template updated to match: cherry-pick references reframed as historical or pointed at UPSTREAM_SYNC.md for the current state. NOTICE.md keeps the BetterTTV cherry-pick example as a concrete past case but adds a paragraph that the pipeline is closed and clarifies the attribution standard is preserved unchanged. PULL_REQUEST_TEMPLATE.md drops the "Upstream cherry-pick from Chat 2" checkbox and the cherry-pick-path compatibility prompt. The upstream git remote was already removed locally on 2026-05-08 (separate change, not in this commit). No source-file edits, no manifest version bump, no changelog entry — this is documentation-only and ships with the next release.
71 lines
2.2 KiB
Markdown
71 lines
2.2 KiB
Markdown
<!--
|
|
Thanks for contributing to HellionChat. Please fill in the sections
|
|
below so the review goes quickly. Delete sections that genuinely do
|
|
not apply, but do not delete the whole template.
|
|
|
|
If this is a security fix, stop here and use a private security
|
|
advisory instead:
|
|
https://github.com/JonKazama-Hellion/HellionChat/security/advisories/new
|
|
-->
|
|
|
|
## Summary
|
|
|
|
<!-- One or two sentences. What does this PR change and why. -->
|
|
|
|
## Type of change
|
|
|
|
<!-- Tick all that apply. -->
|
|
|
|
- [ ] Bug fix (non-breaking change that fixes an issue)
|
|
- [ ] New feature (non-breaking change that adds behaviour)
|
|
- [ ] Breaking change (config migration, removed feature, or behaviour
|
|
change that user-visible defaults rely on)
|
|
- [ ] Documentation only
|
|
- [ ] Translation update
|
|
- [ ] Build, CI or tooling change
|
|
|
|
## Linked issue
|
|
|
|
<!-- e.g. "Closes #42" or "Refs #42". For trivial typo fixes, "n/a". -->
|
|
|
|
## How I tested this
|
|
|
|
<!--
|
|
- Built locally with `dotnet build -c Release`
|
|
- Ran `dotnet test`
|
|
- Loaded the plugin in-game on Windows / Linux / macOS via XIVLauncher
|
|
- Specific scenarios I exercised in-game
|
|
-->
|
|
|
|
## User-visible changes
|
|
|
|
<!--
|
|
Anything the end user will notice. New settings, changed defaults,
|
|
new commands, new translations, removed behaviour. If none, write
|
|
"none".
|
|
-->
|
|
|
|
## Compatibility notes
|
|
|
|
<!--
|
|
- Does this require a configuration migration? If yes, which version
|
|
bump and is it covered by the existing migration tests?
|
|
- Does this change the schema in MessageStore?
|
|
- Does this change the repo.json or HellionChat.yaml manifest fields?
|
|
-->
|
|
|
|
## Checklist
|
|
|
|
- [ ] I have read [CONTRIBUTING.md](../CONTRIBUTING.md) and
|
|
[CODE_OF_CONDUCT.md](../CODE_OF_CONDUCT.md).
|
|
- [ ] My change matches the existing code style (`.editorconfig`).
|
|
- [ ] I added or updated tests where the existing test infrastructure
|
|
made that practical, or I have explained why tests are not
|
|
applicable.
|
|
- [ ] I updated the README, in-plugin strings or documentation if my
|
|
change is user-visible.
|
|
- [ ] I did not include any AI-generated code without disclosing it
|
|
in the PR description (see [AI_DISCLOSURE.md](../docs/AI_DISCLOSURE.md)).
|
|
- [ ] I confirm my contribution is released under the
|
|
[EUPL-1.2](../LICENSE).
|