Awesome-list integration #24
Closed
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
uint
reviewed
Nov 22, 2022
There was a problem hiding this comment.
Awesome! I appreciate the more succinct phrasing, typo fixes, badges, and everything.
If we're switching to a different linter, would you mind deleting .prettierrc.json while we're here? It would be misleading now.
uint
approved these changes
Nov 22, 2022
|
You're right. I deleted the old linter file and added the .yml config file for the automatic PR check. |
|
Re-requesting a review automatically removed @pyramation from reviewers and I don't have the authority to add him again. FYI. |
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.
Several changes for awesome-list compatibility are applied
This PR is a follow-up for the file changes mentioned in issue #22. After this is merged, the repository settings mentioned in the issue can be applied.
@uint