aspiers / aspiers/vc-osc

Before commiting make sure the changes file is updated

Open
#2 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Emacs Lisp
Stars
5
Forks
3
PR merge metrics
No merged PRs in 30d

Description

When I edit and the spec file and then I use the vc-next-action I am actually expecting to write the changes file. But in reality I am commiting the file I have edited. Would it be possible to force a check and before the next action of commiting goes on the user is provided with the chance of updating the changes file.

It could be as well be that I am using the package wrong

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the workflow described: edit the spec file, invoke vc-next-action, and observe when the changes file is committed. Then trace the vc-next-action integration in this Emacs VC backend. Done means the commit step checks for the changes file and gives the user an opportunity to update it first.

Written by the indexing model from the issue text.

Assessment

Tech stack
emacs-lisp
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.