mirror of
https://github.com/artiebits/fake-git-history.git
synced 2026-04-26 15:35:58 +03:00
[PR #22] [MERGED] Implementation of the exec() call in Promise mode #41
Labels
No labels
good first issue
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-git-history#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/artiebits/fake-git-history/pull/22
Author: @quentingosset
Created: 11/18/2020
Status: ✅ Merged
Merged: 11/20/2020
Merged by: @artiebits
Base:
master← Head:patch-1📝 Commits (1)
586b322Implementation of the exec() call in Promise mode📊 Changes
1 file changed (+20 additions, -4 deletions)
View changed files
📝
src/index.js(+20 -4)📄 Description
I don't know why I had this problem, but I noticed that I always had a limit of 1 to 3 commits for each day using the --commitsPerDay option "5,10" (see screen) however in the debug the value commitsPerDay was always higher than 3 and in the commit creation loop there were the X commits sent. however during a "git log" only 3 commits maximum per day were present. So I suspect a problem with the exec() and the waiting of 150. I solved the problem by using an exec in Promise mode.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.