You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using auto to automatically publish packages from Git repositories, it can be time-consuming and unnecessary for auto to iterate through the entire commit history, especially for repositories with a long history. This can result in performance issues and delays in publishing.
Describe the solution you'd like
I would like to see the addition of one of the two features to address this problem:
1-) The ability to set a specific commit as the starting point for auto. This would allow users to specify a commit where they know the package is already up-to-date, so that auto does not need to traverse the entire commit history.
2-) The ability to limit the total number of commits that auto should navigate. For example, users could set a limit of 100 commits from the latest commit, so that auto only needs to examine the most recent 100 commits. This would help to improve performance and reduce unnecessary iterations over the Git history.
The text was updated successfully, but these errors were encountered:
I think there is probably a place where we can limit auto from parsing more commits. I'm not really sure where that might be at the moment. If you want to submit a PR with investigations I'd be happy to Shepard that PR. At the time unfortunately I don't see myself doing this soon.
Is your feature request related to a problem? Please describe.
When using auto to automatically publish packages from Git repositories, it can be time-consuming and unnecessary for auto to iterate through the entire commit history, especially for repositories with a long history. This can result in performance issues and delays in publishing.
Describe the solution you'd like
I would like to see the addition of one of the two features to address this problem:
1-) The ability to set a specific commit as the starting point for auto. This would allow users to specify a commit where they know the package is already up-to-date, so that auto does not need to traverse the entire commit history.
2-) The ability to limit the total number of commits that auto should navigate. For example, users could set a limit of 100 commits from the latest commit, so that auto only needs to examine the most recent 100 commits. This would help to improve performance and reduce unnecessary iterations over the Git history.
The text was updated successfully, but these errors were encountered: