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.

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

Use 100% width for nav buttons #370

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
3 participants
@Blendify
Contributor

Blendify commented Mar 4, 2017

Sorry about this but my fork got corrupt when my computer decided to turn off mid pushing changes.
This is an updated version of #366

I am not sure how to handle the merge conflicts though...

@ericholscher

This comment has been minimized.

Show comment
Hide comment
@ericholscher

ericholscher Mar 5, 2017

Member

All good -- the merge conflicts are an artifact checking them into the repo -- we should probably remove them from the repo and have building them be part of the release process.

Member

ericholscher commented Mar 5, 2017

All good -- the merge conflicts are an artifact checking them into the repo -- we should probably remove them from the repo and have building them be part of the release process.

@agjohnson

This comment has been minimized.

Show comment
Hide comment
@agjohnson

agjohnson Mar 10, 2017

Collaborator

See #379 for a discussion on changing packaging. I don't think we can get ride of these files, but can change expectations on building for PRs.

Collaborator

agjohnson commented Mar 10, 2017

See #379 for a discussion on changing packaging. I don't think we can get ride of these files, but can change expectations on building for PRs.

@Blendify Blendify closed this Mar 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment