open-source-tooling
Here are 29 public repositories matching this topic...
There are about ~240 URLs and licenses listed at https://directory.fsf.org/wiki?title=Category:License
We should:
- ensure that we can detect all of them
- ensure that we can detect their URL
We should also add as an "other_urls" ech URL to the corresponding license YAML
Is your feature request related to a problem? Please describe.
The bot currently decides whether to 'init' (install the placeholders for the table and badge) for the README if there is no .all-contributorsrc
file. If the file is found, it skips this step. This causes the bot to crash if a user has an .all-contributorsrc
file but has nothing else.
Describe the solution you'd like
H
I posted an issue related to this on the main all-contributors repo, however it seems this is where the badge originates. Relevant Issues:
- all-contributors/all-contributors#361 - New Badge Style Preventing Inline Badge
- all-contributors/all-contributors#406 - Change to new badge
I have just had a PR deployed for a custom badge for all-contributors, which is now live meaning we can move a
Especially when the match is not very close it could be useful to be able to pick other near matches from a drop-down to compare to. One situation where I wanted to do this was a BSD-1-Clause license, which I wanted to compare to BSD-3-Clause to see what's the diff between those two (not trusting that it's solely the omission of two clauses).
Absolutely love Askalono, btw.
-
Updated
Jun 24, 2020 - Ruby
-
Updated
May 30, 2020 - Kotlin
Some bizarre use of undefined
as a fixed key in a struct.
-
Updated
Nov 21, 2020 - HCL
-
Updated
Dec 23, 2020 - TypeScript
-
Updated
Dec 12, 2020
-
Updated
Apr 14, 2020
-
Updated
Dec 24, 2020 - Python
As per all-contributors/all-contributors#416 (comment) we should be able to merge based on the login
field instead. This should always be there and be unique, while profile
may not be unique.
We should add an input parameter that lets the user decide what field should be merged on.
We should also add that to the docs and reference the above discussion
-
Updated
May 18, 2020 - Makefile
-
Updated
May 17, 2020 - Makefile
-
Updated
May 17, 2020 - Makefile
-
Updated
May 13, 2020 - Shell
-
Updated
May 13, 2020 - Makefile
pre-cursor / ws
-
Updated
May 13, 2020 - Shell
-
Updated
May 12, 2020
-
Updated
May 17, 2020 - Makefile
-
Updated
May 17, 2020 - Makefile
-
Updated
Feb 10, 2019
-
Updated
May 17, 2020 - Makefile
-
Updated
May 17, 2020
-
Updated
May 17, 2020 - Makefile
Improve this page
Add a description, image, and links to the open-source-tooling topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the open-source-tooling topic, visit your repo's landing page and select "manage topics."
We're in the process of moving all of our documentation to a central location #142. This place is the website, and before we can complete this, we need to translate the website (coming in all-contributors/legacy-domain-landing-page#14)
If you've ever wanted to contribute and help the cause of open source, now is your chance. We need you!
We're looking for translation help for the docume