Recent Developments #424
Merged
Recent Developments #424
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Ready for review] Added option to run chips from the pipeline
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Recent Development
This pull request is a staging area for the changes and improvements that will be added to AIrsenal in its next release, which are described below. If you would like to try these changes before release you can reinstall AIrsenal from our
developbranch - there are instructions in the readme (but note that there may be bugs or undocumented changes).New Features
Enhancements
airsenal_run_pipeline([Ready for review] Added option to run chips from the pipeline #422)Bug Fixes
seasoninSquad.get_sell_price_for_playerWhen this PR is ready to merge:
Before merging: Update the AIrsenal package version in
airsenal/__init__.py. If newfeatures have been added increment the middle number, e.g. 1.1.0 -> 1.2.0,
or if bug fixes only change the last number, e.g. 1.1.0 -> 1.1.1.
After merging: Create a new release
tagged with the new version number. The release text should include the changes above.