Skip to content

Conversation

astonizer
Copy link

@astonizer astonizer commented Oct 1, 2020

Types of changes

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@Smankusors
Copy link

@DanielRuf hmm should we merge this directly at materializecss/materialize repo? or @astonizer need to create another PR there?

@DanielRuf
Copy link
Contributor

It would be great if @astonizer could provide a PR there.

@astonizer
Copy link
Author

Sure, I'll create the PR at materializecss/materialize repo. So the future contributions should be made on this repo or the materializecss/materialize repo, I'm confused.

@DanielRuf
Copy link
Contributor

https://github.com/materializecss/materialize is an actively maintained fork.

This here is mostly the opposite.
See https://github.com/Dogfalo/materialize/commits/v1-dev

@LoganTann
Copy link

Hi y'all any updates about the PR ?

@BraianS
Copy link

BraianS commented May 4, 2024

Good morning guys. Any updates on this pull request? Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants