Skip to content

Commit

Permalink
Merge branch 'new-version'
Browse files Browse the repository at this point in the history
  • Loading branch information
IonicaBizau committed Oct 29, 2022
2 parents 8f5e5a3 + 699a539 commit f8dbe07
Show file tree
Hide file tree
Showing 4 changed files with 1,081 additions and 10 deletions.
2 changes: 1 addition & 1 deletion LICENSE
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
The MIT License (MIT)

Copyright (c) 2014-20 Ionică Bizău <[email protected]> (https://ionicabizau.net)
Copyright (c) 2014-22 Ionică Bizău <[email protected]> (https://ionicabizau.net)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
Expand Down
10 changes: 5 additions & 5 deletions lib/templates/CONTRIBUTING.ejs
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# :eight_spoked_asterisk: :stars: :sparkles: :dizzy: :star2: :star2: :sparkles: :dizzy: :star2: :star2: Contributing :star: :star2: :dizzy: :sparkles: :star: :star2: :dizzy: :sparkles: :stars: :eight_spoked_asterisk:

So, you want to contribute to this project! That's awesome. However, before
doing so, please read the following simple steps how to contribute. This will
make the life easier and will avoid wasting time on things which are not
doing so, please read the following simple steps explaining how to contribute. This will
make life easier and help avoid wasting time on things that are not
requested. :sparkles:

## Discuss the changes before doing them
- First of all, open an issue in the repository, using the <% if (_.pack.bugs) { %>[bug tracker][1]<% } else { %>bug tracker <% } %>,
- First of all, open an issue in the repository, using the [bug tracker][1],
describing the contribution you would like to make, the bug you found or any
other ideas you have. This will help us to get you started on the right
foot.
Expand All @@ -15,9 +15,9 @@ requested. :sparkles:
system, Node.JS version etc.), screenshots (so we can see what you are
seeing).

- It is recommended to wait for feedback before continuing to next steps.
- It is recommended to wait for feedback before continuing the next steps.
However, if the issue is clear (e.g. a typo) and the fix is simple, you can
continue and fix it.
continue to fix it.

## Fixing issues
- Fork the project in your account and create a branch with your fix:
Expand Down
Loading

0 comments on commit f8dbe07

Please sign in to comment.