A small nonprofit exports donation entries from several spreadsheets. Its Python importer currently accepts an optional receipt reference; the new approved specification requires preserving leading zeros and rejecting an empty reference in one workflow. One edit to the parser can leave neighboring tests, error messages, or documentation out of sync. GitHub Copilot Next Edit Suggestions can propose related edits in Visual Studio Code, but proposals are not a tested migration. This hypothetical change demonstrates a reviewable developer workflow rather than claiming AI will automatically make the application correct.
Freeze the schema change in plain language
Before opening Copilot, write a short change request with accepted CSV headers, whether receipt references are strings, which rows may omit a reference, and the exact error when a required value is blank. A reference like 00047 must not be silently converted into integer 47. Define the compatibility policy for existing historical imports as well. If the business owner wants to change only validation, do not allow an AI suggestion to rearrange unrelated file paths or accounting logic.
Collect a representative synthetic fixture with valid, blank, duplicate, and malformed references. Avoid testing on actual donor information or a private export copied into a model prompt. Record the current test status before editing. A clear, narrow specification helps a developer distinguish a helpful related edit from a broad, unrequested code rewrite.
Understand where next edit proposals come from
Visual Studio Code documentation distinguishes ghost-text inline completions from Next Edit Suggestions, which infer nearby or elsewhere-in-file changes from the developer’s recent edits. The documented setting is github.copilot.nextEditSuggestions.enabled. A proposal may appear with a gutter arrow showing its location. The editor provides navigation and acceptance controls, but the developer still decides which suggestions are relevant. Plan and Agent Mode are different tools and should not be assumed to share the same behavior.
Check that the VS Code installation and GitHub Copilot entitlement support the feature. A free allowance and organizational policy can affect availability. Keep the project in a separate version-control branch and review what Copilot displays before accepting it. The process illustration shows an intentional manual schema edit followed by a proposed test change and an independent test run.
Make one intentional parser edit first
Change the code path that reads the receipt field, preserving its text representation and trimming only the whitespace the specification allows. Verify that the importer still distinguishes missing column, empty string, and a legitimate value containing leading zeros. Avoid automatically casting references to numeric types. A single small edit gives the editor a clear recent change from which it may suggest related modifications.
Inspect the actual diff after every acceptance. A proposed update to a test name might be reasonable, while a proposed removal of a validation branch could bypass the point of the ticket. If the suggestion changes the handling of errors or other columns, reject it and write a narrower change. Source control is the audit trail; an AI explanation is not the audit trail.
Review suggested test changes instead of accepting blindly
When Next Edit Suggestions points toward a unit test, verify the expected value against the written acceptance criteria. One correct case is insufficient. Test a leading-zero value, a blank mandatory field, a missing optional column under the old schema, and an invalid row that must not enter the final ledger. If Copilot proposes rewriting fixtures, inspect whether its replacements accidentally erase the edge case.
The comparison graphic shows a misleading test that casts 00047 to 47 beside an accepted test that compares the string 00047. Both are educational sketches, not live traces of Copilot. They illustrate why passing tests can still encode the wrong behavior. The useful outcome is a specification that tests the real risk, not a larger number of green checks.
Run more than the nearest test
Run the targeted parser unit tests, integration tests for representative input files, and the existing validation suite. Check what happens when two rows contain the same receipt code but different donor records: the tool must follow the approved duplicate policy, not infer equality merely from a shared reference. If the importer produces an error report, verify that it identifies the correct row without exposing unnecessary personal details.
A suggested edit might make the narrow unit test pass while changing the public error contract. Compare output fixtures and error messages with the last released version. A regression failure needs investigation before merging, even if Copilot makes another suggestion that hides it. Keep performance claims and import counts out of editorial documentation unless they were measured.
Inspect dependencies, typing and documentation
Review function signatures, type hints, comments and user-facing instructions after the code change. If receipt IDs are now strings, any downstream JSON exporter, database model, or sorting function that treated them as numbers needs inspection. Search the project for the old field rule and note each relevant occurrence. Do not rely on suggestions to locate every reference across modules or disconnected services.
The developer can use normal search, static checks and code review tools alongside Copilot. Document intentional backward-compatibility behavior so a future contributor knows why the field remains textual. Avoid merging purely cosmetic AI changes into the same pull request; they make the safety-related validation change harder to audit.
Keep the review human and the data synthetic
Before asking another engineer to review, remove unapproved sample data from fixtures and commit history. Use fabricated records or anonymized test inputs, respecting organizational policy. A review description should state the user-visible behavior, affected functions, test commands actually run, and known limitations. Do not state that Copilot has formally verified the migration or that every imported record is correct.
Ask a second person to compare the code diff to the acceptance criteria, especially missing values and leading zeros. Review the ability to roll back if the revised importer encounters an unexpected file format. AI can suggest edits, but a human maintainer owns validation, privacy, and deployment decisions.
Merge only after a precise release gate
The final graphic annotates three inspection points: the header mapping, the reference parser, and the regression tests. Require a clean diff without unrelated file edits, a documented test run, and an explicit reviewer approval. Deploy through the project’s normal release process and preserve an unchanged source CSV for troubleshooting. Any production migration requires a separate data-handling plan.
If next-edit proposals are unavailable, the same workflow remains valid with manual edits. This distinction prevents the article from presenting a subscription feature as a prerequisite for good software engineering. The best result is code that follows the approved CSV contract and a test suite that would catch a broken change tomorrow.
How We Research
For this editorial walkthrough, we read official product guidance and checked feature names and restrictions: Visual Studio Code, Inline suggestions from GitHub Copilot; Visual Studio Code, AI settings reference. We compared the vendor descriptions with the specific workflow in this article, then identified where a responsible operator must return to primary records, recorded footage, source code or a current policy owner. The examples, numerical labels and comparisons are hypothetical instructional diagrams, not measured outputs of live product tests. We did not use a connected customer account, claim real grant eligibility, perform original video interpolation measurements or obtain consent for real participants. Available menus, usage limits and plan entitlements can change; readers should consult the latest official documentation and preserve their authoritative source before carrying out the workflow.
Frequently Asked Questions
The editor shows proposed edits that you navigate and accept or dismiss. Inspect every diff before committing.
No. Next Edit Suggestions are inline proposals based on recent changes; agent workflows are separate.
It can suggest an implementation, but tests must verify that 00047 remains a string with its zeros.
Check missing columns, invalid values, downstream exports, error messages and regression fixtures.
Use synthetic records and follow your organization’s privacy rules; a tutorial does not need real donor information.