[GH-ISSUE #8] Commiting should only be possible when no other commits have been started #7

Open
opened 2026-02-26 04:36:13 +03:00 by kerem · 0 comments
Owner

Originally created by @masbicudo on GitHub (Feb 3, 2017).
Original GitHub issue: https://github.com/masbicudo/LetsEncrypt-Certificate-Creator/issues/8

While a commit is not committed, a new commit is not possible.
The UI should state this to the user, and start the retry counter, or wait until it can commit.

Also, if there are commits not yet pushed to the origin, there should be a visual indication, so that the user knows that all previous commits will be pushed.

Originally created by @masbicudo on GitHub (Feb 3, 2017). Original GitHub issue: https://github.com/masbicudo/LetsEncrypt-Certificate-Creator/issues/8 While a commit is not committed, a new commit is not possible. The UI should state this to the user, and start the retry counter, or wait until it can commit. Also, if there are commits not yet pushed to the origin, there should be a visual indication, so that the user knows that all previous commits will be pushed.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/LetsEncrypt-Certificate-Creator-masbicudo#7
No description provided.