Skip to content

[NO-TICKET] Publish/release related fixes, all-contributors setup, pull request template, .gitignore, docs and minor fixes#4

Merged
Ifycode merged 8 commits intodevelopfrom
@GH-MF-1
Mar 6, 2026
Merged

[NO-TICKET] Publish/release related fixes, all-contributors setup, pull request template, .gitignore, docs and minor fixes#4
Ifycode merged 8 commits intodevelopfrom
@GH-MF-1

Conversation

@Ifycode
Copy link
Contributor

@Ifycode Ifycode commented Mar 5, 2026

This pull request makes the following changes

  • Fixes related to publishing/releasing as an npm package
  • Adds .gitignore to project
  • Adds pull request template to project
  • Adds All contributors setup to project
  • Fixes typos, clarity, and makes other minor corrections to user & contributor docs

General checklist

  • My pull request adheres to the community pull request guidelines.
  • I have read and understood the Pull request guideline extension section found at the bottom of this pull request description/body.

Pull request guideline extension

Note

Do not remove this note or section. This talks about extra things to take note of, in addition to the directions given in the community pull request guidelines.

We appreciate the time taken to help tackle issue tickets our community. Please go ahead to submit your pull request even if it is not yet completed, and push to the pull request actively. This will allow us to know that you have not abandoned the issue ticket. However, you should only alert reviewers about your pull request as explained below, to avoid flooding their GitHub notifications unnecessarily.

"Ready for review" implies that things are working as expected, according to how it is specified in the issue ticket you are working on. Ensure that you test the code that you are working on, that it works as expected. Don't just request for review when your pull request is not yet done and working.

The only time you should be making people review something incomplete is: if you want to show them what's not working, so that they can send help or guidance. If this is the case, be explicit about this in our Discord community or in the comment of your pull request (after you have submitted the pull request).

@Ifycode Ifycode changed the title [NO-TICKET-FIX] All contributors setup, pull request template, .gitignore and minor fixes [NO-TICKET] All contributors setup, pull request template, .gitignore and minor fixes Mar 5, 2026
@Ifycode Ifycode changed the title [NO-TICKET] All contributors setup, pull request template, .gitignore and minor fixes [NO-TICKET] Publish/release related fixes, all-contributors setup, pull request template, .gitignore, docs and minor fixes Mar 6, 2026
@Ifycode Ifycode merged commit 5b1b490 into develop Mar 6, 2026
6 checks passed
@Ifycode Ifycode deleted the @GH-MF-1 branch March 6, 2026 00:48
@Ifycode
Copy link
Contributor Author

Ifycode commented Mar 6, 2026

@all-contributors please add @Ifycode for code and doc

@allcontributors
Copy link
Contributor

@Ifycode

I've put up a pull request to add @Ifycode! 🎉

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.

1 participant