repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
sindresorhusawesome | add swiftyedit to cms section | Invalid | readme it s an open source content management system and totally free by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it instead use 2242 for incubation visibility don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion comment point out lint violation be allow but do not count as a review you have read and understand the instruction for create a list this pull request have a title in the format add name of list it should not contain the word awesome add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software no blockchain relate list the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js do not use hard wrapping do not include a ci e g github action badge you can still use a ci for linte but the badge have no value in the readme do not include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add bencher | Invalid | bencher be a suite of continuous benchmarking tool design to catch performance regression in ci that be bencher allow you to detect and prevent performance regression before they make it to production bencher consist of bencher cli bencher api server bencher web ui |
sindresorhusawesome | add asp net | Invalid | this include asp net core which be an enterprise framework and have be around for year asp net be a free cross platform and open source framework for building web app and service with net and c by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it instead use 2242 for incubation visibility run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add django | Invalid | add django to back end development list insert url to the list here readme explain what this list be about and why it should be include here django be a high level python web framework that enable rapid development of secure and maintainable website build by experienced developer django take care of much of the hassle of web development so we can focus on write our app without need to reinvent the wheel by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it instead use 2242 for incubation visibility run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add smollcss | Invalid | this pr add a curate list of snippet for modern css layout and component by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it instead use 2242 for incubation visibility run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add vnstat | Invalid | by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add svgview | Invalid | svgview explain what this list be about and why it should be include here there be no svg parser yet neither in here nor build in into swift or swiftui by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add gradient generator javascript | Invalid | a gradient generator web app build with html and javascript make your gradient with direction with a single click |
sindresorhusawesome | gaming game accessibility guideline | Invalid | insert url to the list here explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add beryldb | Invalid | add beryldb insert url to the list here explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the title of your entry should be title case and the url to your list should end in readme example software architecture readme the discipline of designing and building software the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add bootstrap 5 cheatsheet | Invalid | bootstrap 5 cheatsheet it be an interactive list of bootstrap 5 class variable and mixin it also help you easily find the difference between bootstrap 4 and bootstrap 5 besides it be the only bootstrap 5 cheatsheet you will ever need whether you be upgrade your bootstrap 4 project or start a new bootstrap 5 project furthermore it be aim towards a large community of bootstrap user who find it difficult to search for bootstrap class variable and mixin thus you ll surely find it amazing and very useful key feature search for your class variable or mixin highlight difference between bootstrap 4 5 class also live preview of html code snippet update code snippet on the go easily copy the code snippet and use it useful link website github |
sindresorhusawesome | add moldy to the miscellaneous field | Invalid | explain what this list be about and why it should be include here a opensource project and tool for help to the world by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add moldy add miscellaneous update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add chef to the list | Invalid | it be a configuration management software write in ruby |
sindresorhusawesome | add bolt cms | Invalid | thank for create and maintain the awesome list get to say maybe it s I but the instruction below be extremely unclear be a list like an entry hope I do everything right insert url to the list here link to what list explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add chart css | Invalid | css datum visualization framework by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add appcircle | Invalid | this repo contain a list of appcircle workflow with sample app tutorial and resource to help you learn a mobile devop platform for continuous integration by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add spring boot url | Invalid | spring boot help you to create spring power production grade application and service with absolute minimum fuss it take an opinionated view of the spring platform so that new and exist user can quickly get to the bit they need by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add icon font customization | Invalid | add icon font customization a collection of over 33 000 high quality free svg icon and tool for generate customize icon font a collection of over 33 000 high quality free svg icon and tool for generate customize icon font by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none must not feature contribute or footnote section have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name text or a licence section to the readme github already show the license name and link to the full text at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you it can optionally be link from the readme in a dedicated section title contribute position at the top or bottom of the main content the section should not appear in the table of content all non important but necessary content like extra copyright notice hyperlink to source pointer to expansive content etc should be group in a footnote section at the bottom of the readme the section should not be present in the table of content have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | inital commit | Invalid | insert url to the list here explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name or text to the readme github already show the license name at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add cryptocrit to decentralised project | Invalid | it s not a list it s an open source project by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name or text to the readme github already show the license name at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t use hard wrapping doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add tsparticle | Invalid | add tsparticle to miscellaneous it s a javascript library for easily create particle animation support also reactjs vuejs angular svelte and other it have documentation wiki mit license and actively maintain |
sindresorhusawesome | add balmj | Invalid | a flexible front end workflow for webapps by submit this pull request I confirm I ve read and comply with the below requirement |
sindresorhusawesome | add linkedin learning under learn | Invalid | insert url to the list here explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name or text to the readme github already show the license name at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add development stat for github profile readme | Invalid | profile readme be a recently add feature to github allow you to add a readme to your github profile preview it when your profile be open this repo be mean to showcase tool and other metric use to dynamically update readme with content by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name or text to the readme github already show the license name at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add cirq | Invalid | readme cirq be a python library for write manipulating and optimize quantum circuit and run they against quantum computer and simulator by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration just comment look good or simply mark the pull request as approve do not count you have to actually point out mistake or improvement suggestion you have read and understand the instruction for create a list create list md this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it the default branch should be name main not master include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome md awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name or text to the readme github already show the license name at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline awesome md include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add gatsby | Invalid | gatsby be an ssg static site generator opensource base on react that aim to make development easy and more efficient gatsby be a framework that bring together the main feature of react and several other modern tool in the same package facilitate the creation of fast and powerful website and web application gatsby be an ssg static site generator opensource base on react that aim to make development easy and more efficient gatsby be a framework that bring together the main feature of react and several other modern tool in the same package facilitate the creation of fast and powerful website and web application with gatsby you can develop in react and when you build your code it will generate static file that will be access by user this bring several advantage to your site like seo support incredible speed cache system and several other item the gatsby community also offer a number of pre develop plugin and website so you can start your project halfway by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it run awesome lint on your list and fix the report issue if there be false positive or thing that can not shouldn t be fix please report it include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the repo name of your list should be in lowercase slug format awesome name of list awesome swift awesome web typography awesome swift awesomewebtypography the head title of your list should be in title case format awesome name of list awesome swift awesome web typography awesome swift awesomeswift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything do not contain item that be unmaintaine have archive repo deprecate or miss doc if you really need to include such item they should be in a separate markdown file include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license we strongly recommend the cc0 license but any creative common license will work tip you can quickly add it to your repo by go to this url replace and accordingly a code license like mit bsd apache gpl etc be not acceptable neither be wtfpl and unlicense place a file name license or license in the repo root with the license text do not add the license name or text to the readme github already show the license name at the top of the repo to verify that you ve read all the guideline please comment on your pull request with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add firebird sql server to database | Invalid | add firebird sql server to database |
sindresorhusawesome | add lucid kv | Invalid | lucid be a high performance and distribute kv store accessible through an http api write in rust |
sindresorhusawesome | add neo mjs | Invalid | add neo mj to the list of framework neo mjs be a webworker drive ui framework use es8 |
sindresorhusawesome | update readme md | Invalid | we make a spreadsheet for tech referral it would be great if anyone be willing to add their name and offer referral for your current or previous company |
sindresorhusawesome | add mermaid | Invalid | add mermaid generation of diagram and flowchart from text in a similar manner as markdown a pretty cool diagram editor that can be use with by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement |
sindresorhusawesome | add django | Invalid | django readme django be a high level python web framework that encourage rapid development and clean pragmatic design build by experienced developer it take care of much of the hassle of web development so you can focus on write your app without need to reinvent the wheel it s free and open source by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the head title of your list should be in the follow format awesome name of list awesome swift awesome web typography awesome swift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc wtfpl and unlicense be not acceptable license if you use a license badge it should be svg not png to verify that you ve read all the guideline please add comment with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add arangodb in readme md | Invalid | add arangodb in the database list insert url to the list here explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request don t waste my time do a good job adhere to all the guideline and be responsive you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration you have read and understand the instruction for create a list this pull request have a title in the format add name of list add swift add software architecture update readme md add awesome swift add swift add swift add swift your entry here should include a short description about the project theme of the list it should not describe the list itself the first character should be uppercase and the description should end in a dot it should be an objective description and not a tagline or marketing blurb ios mobile operating system for apple phone and tablet framer prototype interactive ui design ios resource and tool for io development framer framer prototype interactive ui design your entry should be add at the bottom of the appropriate category the suggest awesome list complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent don t open a draft wip pull request while you work on the guideline a pull request should be 100 ready and should adhere to all the guideline when you open it include a succinct description of the project theme at the top of the readme example mobile operating system for apple phone and tablet prototype interactive ui design resource and tool for io development awesome framer package and tool it s the result of hard work and the good I could possibly produce if you have not put in considerable effort into your list your pull request will be immediately close the head title of your list should be in the follow format awesome name of list awesome swift awesome web typography awesome swift non generate markdown file in a github repo the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate please search for exist submission only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc wtfpl and unlicense be not acceptable license if you use a license badge it should be svg not png to verify that you ve read all the guideline please add comment with just the word unicorn have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme doesn t include an inspire by awesome foo or inspire by the awesome project kinda link at the top of the readme the awesome badge be enough go to the top and read it again |
sindresorhusawesome | add javascript beginner | Invalid | this be an excellent resource for beginner learn javascript exercise be include in the tutorial by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration I have read and understand the instruction for create a list this pull request have a descriptive title in the format add name of list example add swift not update readme md or add awesome list the entry in the awesome list should include a short description about the project theme of the list it should not describe the list itself example fish user friendly shell not fish resource for fish be add at the bottom of the appropriate category the list I m submit complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent it s the result of hard work and the good I could possibly produce non generate markdown file in a github repo include a succinct description of the project theme at the top of the readme example the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc wtfpl and unlicense be not acceptable license if you use a license badge it should be svg not png have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme go to the top and read it again |
sindresorhusawesome | add clojure web framework luminus | Invalid | insert url to the list here explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request you have to review at least 2 other open pull request try to prioritize unreviewe prs but you can also add more comment to review prs go through the below list when review this requirement be mean to help make the awesome project self sustain comment here which prs you review you re expect to put a good effort into this and to be thorough look at previous pr review for inspiration I have read and understand the instruction for create a list this pull request have a descriptive title in the format add name of list example add swift not update readme md or add awesome list the entry in the awesome list should include a short description about the project theme of the list it should not describe the list itself example fish user friendly shell not fish resource for fish be add at the bottom of the appropriate category the list I m submit complie with the below requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent it s the result of hard work and the good I could possibly produce non generate markdown file in a github repo include a succinct description of the project theme at the top of the readme example the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible either center fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head can be place center if the list have a center graphic header should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of nest list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc wtfpl and unlicense be not acceptable license if you use a license badge it should be svg not png have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme go to the top and read it again |
sindresorhusawesome | add minet in game category | Invalid | minet be an interesting open source voxel game |
sindresorhusawesome | add web cache | Invalid | insert url to the list here varnish varnish cache squid squid cache nuster nuster cache explain what this list be about and why it should be include here web cache by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot requirement for your pull request I have read and understand the contribution guideline and the instruction for create a list this pull request have a descriptive title for example add name of list not update readme md or add awesome list the entry in the awesome list should include a short description about the project theme of the list it should not describe the list itself example fish user friendly shell not fish resource for fish be add at the bottom of the appropriate category the list I m submit complie with these requirement requirement for your awesome list have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent it s the result of hard work and the good I could possibly produce non generate markdown file in a github repo include a succinct description of the project theme at the top of the readme example the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible either fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of sub list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc wtfpl and unlicense be not acceptable license if you use a license badge it should be svg not png have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme go to the top and read it again |
sindresorhusawesome | google s flutter add | Invalid | recently publish google s new alternative to react native |
sindresorhusawesome | update readme md | Invalid | add swastika I o core cms insert url to the list here explain what this list be about and why it should be include here swastika I o core cms be all in one platform e g cms forum q a crm base on asp net core dotnet core framework by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot I have read and understand the contribution guideline and the instruction for create a list this pull request have a descriptive title for example add name of list not update readme md or add awesome list the entry in the awesome list should include a short description about the project theme of the list it should not describe the list itself example fish user friendly shell not fish resource for fish be add at the bottom of the appropriate category the list I m submit complie with these requirement have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent it s the result of hard work and the good I could possibly produce non generate markdown file in a github repo include a succinct description of the project theme at the top of the readme example the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible either fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of sub list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc wtfpl and unlicense be not acceptable license if you use a license badge it should be svg not png have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period drop all the a an prefix in the description consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme go to the top and read it again |
sindresorhusawesome | add awesome rainbond | Invalid | rainbond be an application centric paas integrate kubernete base container management ci cd and multiple datum center resource management to provide full management of cloud native application build connection between application and infrastructure application and application infrastructure and infrastructure by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot I have read and understand the contribution guideline and the instruction for create a list this pull request have a descriptive title for example add name of list not update readme md or add awesome list the entry in the awesome list should include a short description about the project theme of the list it should not describe the list itself example fish user friendly shell not fish resource for fish be add at the bottom of the appropriate category the list I m submit complie with these requirement have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent it s the result of hard work and the good I could possibly produce non generate markdown file in a github repo include a succinct description of the project theme at the top of the readme example the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible either fullwidth or place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of sub list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc wtfpl and unlicense be not acceptable license if you use a license badge it should be svg not png have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar the link and description be separate by a dash example ava javascript test runner the description start with an uppercase character and end with a period drop all the a an prefix in the description consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme go to the top and read it again |
sindresorhusawesome | add quasar framework to frontend framework | Invalid | null |
sindresorhusawesome | add scotch io | Invalid | add scotch io such a great site to learn web developtment the good tutorial and content that you ll find for web development guide course tutorial and more great content to learn with |
sindresorhusawesome | add three js of front end development | Invalid | three js javascript 3d library the library provide canvas svg css3d and webgl renderer |
sindresorhusawesome | add etherium | Invalid | insert url to the list here explain what this list be about and why it should be include here by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot I have read and understand the contribution guideline and the instruction for create a list this pull request have a descriptive title for example add name of list not update readme md or add awesome list the entry in the awesome list should include a short description about the project theme of the list it should not describe the list itself example fish user friendly shell not fish resource for fish be add at the bottom of the appropriate category the list I m submit complie with these requirement have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent it s the result of hard work and the good I could possibly produce non generate markdown file in a github repo include a succinct description of the project theme at the top of the readme example the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of sub list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc if you use a license badge it should be svg not png have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar each link description start with an uppercase character and end with a period example ava javascript test runner drop all the a an prefix in the description consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme go to the top and read it again |
sindresorhusawesome | add the blockstack platform | Invalid | blockstack be a new fully decentralized internet that come with a full stack of open source developer tool to build and bootstrap decentralize application and protocol ecosystem developer be actively build decentralize application on blockstack today we have create a vc partner fund for blockstack that be a 25 m fund aim at grow an ecosystem of decentralized application on blockstack the fund be partner with thesis drive venture capital firm who be align with our vision of a decentralized internet like lux capital rise tide compound openocean and versionone to fund app developer and team look to build their app on the new fully decentralized internet app creator will benefit directly from the deep expertise and insight of these experienced investor additionally there be an xprize style prize and bounty for large initiative such as build a decentralized microblogge platform fund by investor like naval ravikant founder angellist albert wenger managing partner usv and more blockstack have raise 4 mm in vc funding by submit this pull request I confirm I ve read and comply with the below requirement please read it multiple time I spend a lot of time on these guideline and most people miss a lot I have read and understand the contribution guideline and the instruction for create a list this pull request have a descriptive title for example add name of list not update readme md or add awesome list the entry in the awesome list should include a short description about the project theme of the list it should not describe the list itself example fish user friendly shell not fish resource for fish be add at the bottom of the appropriate category the list I m submit complie with these requirement have be around for at least 30 day that mean 30 day from either the first real commit or when it be open source whatever be most recent it s the result of hard work and the good I could possibly produce non generate markdown file in a github repo include a succinct description of the project theme at the top of the readme example the repo should have awesome list awesome as github topic I encourage you to add more relevant topic not a duplicate only have awesome item awesome list be curation of the good not everything include a project logo illustration whenever possible place at the top right of the readme example the image should link to the project website or any relevant website the image should be high dpi set it to maximum half the width of the original image entry have a description unless the title be descriptive enough by itself it rarely be though include the awesome badge awesome badge should be place on the right side of the readme head should link back to this list have a table of content section should be name content not table of content should be the first section in the list should only have one level of sub list preferably none have an appropriate license choose an appropriate license that mean something like cc0 not a code licence like mit bsd apache etc if you use a license badge it should be svg not png have contribution guideline include contribution guideline the file should be name contribute md casing be up to you have consistent formatting and proper spelling grammar each link description start with an uppercase character and end with a period example ava javascript test runner drop all the a an prefix in the description consistent and correct naming for example node js not nodejs or node js doesn t include a travis badge you can still use travis for list linte but the badge have no value in the readme go to the top and read it again |
sindresorhusawesome | let s add description to entry | Enhancement | I could use some help add description to entry in this list the description should be as succinct as possible short but descriptive they should be about the project theme not the list itself if you decide to do a pr please do at least 10 description correct ava test runner not correct ava full featured test runner with magic unicorn and many other thing not correct ava resource for ava not correct ava awesome resource not correct ava list of testing resource |
sindresorhusawesome | how to grow awesome | Question | the awesome list concept have turn out to be very popular with a great community around it I m wonder what else we could do with the awesome brand would there be any interest in an awesome meetup maybe a blog highlight awesome thing email newsletter twitter account would you follow it if so print awesome sock because why not I m open for idea no idea be too weird or crazy or maybe there s no need to do anything more that s a valid comment too |
sindresorhusawesome | encryption list | Help Wanted | maybe someone be interested in create and maintain the awesome ecryption list it might be useful quick googling and search github say that s nothing like it |
sindresorhusawesome | help sort the miscellaneous category | Enhancement | as mention in issuecomment 189576619 it will be helpful if we can go through the miscellaneous section and group resource together to form new category a category should have at least 2 preferably 3 item |
sindresorhusawesome | nosql | Help Wanted | maybe it s too early in the game for this but it would be nice awesome to see a list on nosql datum structure good practice tutorial talk and article some link I ve come across in the past |
sindresorhusawesome | contribute md show info for create list | Enhancement | I think that these info should be move to awesome md completely so we could have a contribute md file that contain only info for submit the content to this list and of course the link to awesome md |
sindresorhusawesome | add badge to exist list | Help Wanted | could use some help with get the badge awesome into exist list comment on which you ve do awesome badge |
sindresorhusawesome | improve the awesome list ecoystem | Help Wanted | a lot of list be miss important thing or just too low of quality we could be nice internet citizen and help out those list common thing I open issue about in list miss license here we can suggest the same as this repo or cc0 or some other cc license miss contribute md can just suggest copy the one in this repo and modify it to own need succinct description to each item commentary on each item add by the submitter of why the item be worth read consume see city in flight 1970 by james blish 40 for example grammar I find an amazing amount of typo in the list people make it s readme should have a clear description of what the list contain quality check add content not everything be worth add it should be a curation of the good not a list of everything have all list follow this would improve the quality considerably maybe we could come up with some guideline on what s a awesome certify list anything I miss anyone care to help out opening issue on list both list include here and not |
publicapispublicapis | dog fact site be break so update readme md | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit dog fact site be break fix it |
publicapispublicapis | api add | Enhancement | my submission be format accord to the guideline in the contribute guide contribute md my addition be order alphabetically my submission have a useful description the description do not have more than 100 character the description do not end with punctuation each table column be pad with one space on either side I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item all change have be squashed squash link into a single commit squash link |
publicapispublicapis | update broken url to late path | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add crossmint nft mint api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add assemblyai api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | update readme md | Enhancement | add an api that return local time for a give location for example america bel m |
publicapispublicapis | add debricke open source select api | Enhancement | add debricke open source select api to open datum x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | fix typo on line 779 in readme from unkown to unknown | Enhancement | this be my first open source commit below be the default text and all I do be fix a typo so I m not sure if the default apply let I know if I need to do anything else my submission be format accord to the guideline in the contribute guide contribute md my addition be order alphabetically my submission have a useful description the description do not have more than 100 character the description do not end with punctuation each table column be pad with one space on either side I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item all change have be squashed squash link into a single commit squash link |
publicapispublicapis | fix the typo in cor field of tax datum api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | update readme md | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md my addition be order alphabetically my submission have a useful description x the description do not have more than 100 character the description do not end with punctuation each table column be pad with one space on either side I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add without auth | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add iaea api | Enhancement | with correct format x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add sahha api | Enhancement | my submission be format accord to the guideline in the contribute guide contribute md my addition be order alphabetically my submission have a useful description the description do not have more than 100 character the description do not end with punctuation each table column be pad with one space on either side I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item all change have be squashed squash link into a single commit squash link |
publicapispublicapis | remove broken link | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add headhunter huntflow and friendwork job service api description update gitignore | Enhancement | hello I want to propose change for several service I ddd headhunter huntflow and friendwork job service api and update gitignore thank |
publicapispublicapis | add hindi joke api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add padel court sweden api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add momoai to machine learning | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | update readme md | Enhancement | add legitimate job search website and app x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add browse ai to the development list | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add cronit | Enhancement | add a link to cronit a new online cronjob scheduling system |
publicapispublicapis | add getblock api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add qr code dynamic and static api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | fix metaweather api url | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | remove metaweather url be not valid | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md my addition be order alphabetically my submission have a useful description the description do not have more than 100 character the description do not end with punctuation each table column be pad with one space on either side I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item all change have be squashed squash link into a single commit squash link |
publicapispublicapis | fix typo in entry for tax datum api 3263 | Enhancement | unkown be now unknown x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | fix break url 404 for open datum archive | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically my submission have a useful description the description do not have more than 100 character the description do not end with punctuation each table column be pad with one space on either side I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add wazirx api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add board game atlas api | Enhancement | add board game atlas api to game comic_strip x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add http cat http garden googlebot and bingbot api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add screenshot you api for screenshot | Enhancement | here you can quickly and free capture a full screenshot of the website with high resolution and without watermark to do this you only need a link to the page from which you want to get a screen capture thank x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add open subtitle api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add thedogapi api to animal | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | update readme md | Enhancement | add repetiti com api x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add datastream api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | fix typo in entry for tax datum api | Enhancement | this propose change do not add a new entry it fix a typo in the entry for tax datum api fix spelling of cor field unkown be incorrect fix spell it unknown as it be spell for all other entry fix 3262 x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add github profile readme generator api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add tradingview api in cryptocurrency | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add meteosource api to weather | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add wattbuy api | Enhancement | add wattbuy api x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add shotstack video editing api | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add shadify to development | Enhancement | my submission be format accord to the guideline in the contribute guide contribute md my addition be order alphabetically my submission have a useful description the description do not have more than 100 character the description do not end with punctuation each table column be pad with one space on either side I have search the repository for any relevant issue or pull request any category I be create have the minimum requirement of 3 item all change have be squashed squash link into a single commit squash link |
publicapispublicapis | memo add arvancloud api link | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | remove metaweather | Enhancement | do no long exist x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add hirak crypto to cryptocurrency | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | add hirak object detection to machine learning | Enhancement | x my submission be format accord to the guideline in the contribute guide contribute md x my addition be order alphabetically x my submission have a useful description x the description do not have more than 100 character x the description do not end with punctuation x each table column be pad with one space on either side x I have search the repository for any relevant issue or pull request x any category I be create have the minimum requirement of 3 item x all change have be squashed squash link into a single commit squash link |
publicapispublicapis | public apis situation read this issue please | Good First Issue | hi community this message be to clarify and make transparent the current situation of public apis in addition to demonstrate the frustration of us maintainer so read this if you find it interesting please well I keep the public apis project together with other 3 developer pawelborkar marekdano and yannbertrand for a long time 1 year ago the public apis project be dead with over 300 open pull request and dozen of unresolved issue we start work and resolve all prs and open issue in about 2 month since then more than 1000 prs have be resolve dozen of issue resolve several improvement to the project and a remarkable growth so it s clear that we ve revive and improve the project see more at over time we have several other idea to far improve the project for the community but we encounter a number of problem that prevent we from execute they many of these issue be relate to our access level in the public apis organization repository as we need to activate special feature in the setting and create new repository in the organization we start make attempt to communicate with people work at apilayer current owner of the public apis organization project to try to help we improve the project but this prove extremely difficult I speak with employee and ex employee but could not get help I also speak to john burr apilayer s general manager but he hasn t respond for many month I make several more attempt to communicate with julian zehetmayr and paul zehetmayr co founder and former ceo of apilayer but get no response I believe they be very busy people see more at issuecomment 793154290 just try to communicate with apilayer to help we improve the project and fail in almost every attempt be frustrating for us maintainer in addition to other problem cause by the apilayer admin user who sometimes make undue modification that cause all our test and project policy to be break see the history of apilayer admin also we notice that this week all of we maintainer have our access level lower without any communication motivation or anything close to that now we don t even have access to the basic setting in the repository so realize how frustrating this be for we but we re still try because we believe it s important to the community we have no idea why apilayer be act this way with us maintainer who help revive and improve the project we just want help and collaboration so that everything work well without harm the community so due to all these problem I have indicate possible solution to help we to apilayer representative apilayer add we as one of the owner or member of the public apis organization with the necessary access to move forward with the project or if apilayer be not interested in maintain and help to evolve the project which we believe give the whole situation transfer it to one of we maintainer so that we can improve it I believe that this be an adequate measure give everything I have describe and it would solve several communication problem that apilayer would not need to deal with in addition of course to help an entire community to improve it all transferring project be very well see by the community and this transfer to the right people who will maintain the project but again I didn t get any straight answer to that then notice how frustrating this be we greatly want apilayer s collaboration and understanding we don t want the project to die again or be use in a way that harm the community with inappropriate addition we just want to help yannbertrand also write about the situation on his blog other link that may be useful for more information issuecomment 989514138 if this issue be permanently delete to hide what I ve describe you can find a permanent record at wayback machine last capture capture history archive today last capture capture history |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.