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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mgrover1 I think this is not the right fix for the problem you were having.
This line was meant to run this workflow step only if executing the notebooks on GitHub Actions. In that case, we need to build an execution environment here.
For executing on binder, the
environment.yml
file is ignored and we just build a minimal JupyterBook + binderbot environment (see this line)If I understand correctly, the problem you were trying to solve is the case where we execute on binder, but there is a change in the
environment.yml
file so a new image needs to be built on the binder. Is that correct? We'll need a different fix for that.Currently the call to binderbot is hard-wired to the
main
branch (this line) so we always use the image associated with current main branch.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification here @brian-rose and sorry for merging without getting more feedback first!