Skip to content

Per-Commit stepping and baseline improvement #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
3 tasks done
Byron opened this issue Nov 20, 2022 · 0 comments
Closed
3 tasks done

Per-Commit stepping and baseline improvement #30

Byron opened this issue Nov 20, 2022 · 0 comments
Labels
enhancement

Comments

@Byron
Copy link
Owner

Byron commented Nov 20, 2022 •
edited
Loading

Various tasks offloaded from #26 with the main purpose of restoring the correct order of crate changes and updating the baseline tests to be more realistic.

Tasks

  1. add support for per-commit stepping to allow for orderly discovery of changes
  2. improve baseline to test big steps and one-commit-per-step (using the new API of above) like ---x---x---xxx
  3. adjust baseline test to inform about the yanked status as well, so we expect that all changes leave us as exactly the right information about the versions still in existence and their yanked status.
@Byron Byron mentioned this issue Nov 20, 2022
Closed
Byron added a commit that referenced this issue Nov 22, 2022
@Byron
feat: baseline also validates the yanked status. (#30)
4dd4a4c 
That way we assure that the state we are interested in is indeed
communicated perfectly through the events we emit.
Byron added a commit that referenced this issue Nov 22, 2022
@Byron
feat: greatly improve performance and realism of baseline-atomic te…
81c6dd2 
…st. (#30)

We now set a fixed amount of 'big' steps along with one of those chunks
being a range where the step-size is one commit at a time, which
might be the way changes are obtained in the future.
Byron added a commit that referenced this issue Nov 22, 2022
@Byron
feat: baseline validation now validates ordered and unordered mode. (#30
87e49b5 
)
Byron added a commit that referenced this issue Nov 22, 2022
@Byron
prepare changelog (#30)
b887560
Byron added a commit that referenced this issue Nov 22, 2022
@Byron
fix: allow to configure the http transport layer in git-repository. (…
327c075 
…#30)

This way the user of the library has a choice to activate any of these
features:

* http-curl (default) - use curl and a lot of C dependencies for HTTP/HTTPS.
  But also support advanced HTTP options.
* http-request - use reqwest for http and https, which currently doesn't
  support any options.
@Byron Byron closed this as completed Nov 22, 2022
Byron added a commit that referenced this issue Nov 22, 2022
@Byron
fix: allow to configure the http transport layer in git-repository. (…
c3cff88 
…#30)

This way the user of the library has a choice to activate any of these
features:

* http-curl (default) - use curl and a lot of C dependencies for HTTP/HTTPS.
  But also support advanced HTTP options.
* http-request - use reqwest for http and https, which currently doesn't
  support any options.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Byron