Skip to content
This repository was archived by the owner on Jan 9, 2020. It is now read-only.

ABOUT_THESE_NOTEBOOKS.md as a suggested order of approach#267

Closed
brianmapes wants to merge 0 commit intoUnidata:masterfrom
brianmapes:master
Closed

ABOUT_THESE_NOTEBOOKS.md as a suggested order of approach#267
brianmapes wants to merge 0 commit intoUnidata:masterfrom
brianmapes:master

Conversation

@brianmapes
Copy link
Copy Markdown
Contributor

That directory is a little blank -- just alphabetical. Could use a bit of a front face. Not sure if this is the right way, but a suggestion.

Copy link
Copy Markdown
Contributor

@jrleeman jrleeman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! At one point we had a table of contents and it kept getting out of date, so we killed it until we can circle back and automate it. I like the about these notebooks file. Maybe we should have it render as part of the website? Thoughts @dopplershift

@dopplershift
Copy link
Copy Markdown
Member

This is a nice outline to have, thanks!

@jrleeman if you have a place where you think this would fit in the rendered docs, I'm all ears. Regardless, this is a nice thing to have alongside the notebooks.

environment.yml Outdated
- pip:
- python-awips
- mpldatacursor
- drilsdown
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brian, did you mean to push this? Because these don't look like changes we should take. If it was a mistake, we can handle.

@brianmapes
Copy link
Copy Markdown
Contributor Author

brianmapes commented Feb 6, 2018 via email

@brianmapes
Copy link
Copy Markdown
Contributor Author

brianmapes commented Feb 6, 2018 via email

@dopplershift
Copy link
Copy Markdown
Member

When you create a pull request, GitHub essentially creates a link between the pull request and the branch you are asking to be "pulled in"--in this case the master branch on your fork of the python workshop materials. Every time you push to that branch, this pull request is updated.

That's a great thing for when we're collaboratively going back and forth on changes, since it means you can easily update a pull request. It's less great in this case. At any rate, that link is severed once the PR is merged, which means it's really our fault for not merging in your contribution in a timely fashion.

@jrleeman
Copy link
Copy Markdown
Contributor

@brianmapes - is it okay if I blast away that environment.yml change? It will go away on your master branch as I would be pushing there.

@brianmapes
Copy link
Copy Markdown
Contributor Author

brianmapes commented Mar 19, 2018 via email

@jrleeman jrleeman closed this Mar 19, 2018
@jrleeman jrleeman mentioned this pull request Mar 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants