Add Copilot repository instructions and path-scoped instruction files - #18
Merged
Merged
Conversation
Copilot created this pull request from a session on behalf of
sbokatuk
July 30, 2026 09:58
View session
sbokatuk
marked this pull request as ready for review
July 30, 2026 10:15
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.
The repository had no agent instructions, so every Copilot session had to rediscover the things that are easy to get wrong here: the dual FFmpeg/FFmpegKit version schemes, the checksum-gated native fetch, and the two-pass pack.
Adds
.github/copilot-instructions.mdplus two path-scoped instruction files. Every command was checked against the script or workflow that runs it (build/resolve-versions.shwas run read-only to confirm both directions and the unmapped-version failure)..github/copilot-instructions.md(~900 words)FFmpegKitBuildType, native.aarfromdev.ffmpegkit-maintainedon Maven Central (arthenica retired), and the two version schemes withbuild/native-versions.tsvas their single source of truth.FFmpegKitSdkBand,--verify, and the baseline-first order for trying a new upstream line.Ffmpegkit.Droidnever moves, build-file comments are load-bearing, British spelling, invariant parsing returningnull; PR beta → merged release note → auto-tag → guarded release; PackageTests always, device script when touchingAdditions/,Transforms/, the.aarwiring or the consumer.targets.FFMPEGKIT001/FFMPEGKIT002onPrepareForBuild, keep the GPL/LGPL split and the non-GPL sample,./artifactsover nuget.org, no hand-edited merged packages, no bypassing the releaseguard..github/instructions/native-versions.instructions.mdapplyTo: "build/native-versions.tsv, build/checksums/**, src/FFmpegKit.Android/Jars/**"— the ordered procedure for adopting a new upstream line: read the FFmpeg version out of the shippedlibavcodec.so, record the baseline, add the mapping row, then bump the props..github/instructions/workflows.instructions.mdapplyTo: ".github/workflows/*.yml"—verifyinput semantics (true on PRs, false on releases), trusted publishing (environment: nuget.org,id-token: write, onlyNUGET_USER, push immediately after login), the releaseguardjob, theauto-release→ dispatch requirement, Linux runners and the x86_64/KVM/disk constraints on the emulator jobs.No code, build or workflow behaviour is changed.