Encapsulate repository fields in config #114
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We want to change these fields to be smarter in the future.
These fields are all fine for the case where there's only an origin repo
that is being worked against. Once we get to wanting to support an
upstream repo for a fork, these fields start to take on a bit more
logic. In an effort to make that step a bit easier, we encapuslate the
direct access to these fields behind functions where that logic can
exist.
This is pre-work for #80 that is
spun out of #106.
Test Plan:
There should be no actual changes here. It should be enough to run
cargo test
and see no failures.