Add Awesome F#

[0exbot]

Pull request from @vasily-kirichenko.

• title: F#
• head: Programming Languages
• url: https://github.com/fsprojects/awesome-fsharp
• stars: 981
• size: 301
• redir: https://github.com/VPashkov/awesome-fsharp
• updated: 2022-08-11 14:20
• created: 2017-04-19 13:53
• pull: Add Awesome F# sindresorhus/awesome#939

Add Awesome F#.

https://github.com/VPashkov/awesome-fsharp

It's list of repos related to F# programming language

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

• I have read and understood the contribution guidelines and the instructions for creating a list.
• This pull request has 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 list project/theme. It should not describe the list itself.
    Example: - [Fish](…) - User-friendly shell.
  • Be added at the bottom of the appropriate category.
• The list I'm submitting complies with these requirements:
  • Has been around for at least 30 days.
    That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • It's the result of hard work and the best I could possibly produce.
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have the following GitHub topics set: awesome-list, awesome, list. I encourage you to add more relevant topics.
  • Not a duplicate.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Includes a project logo/illustration whenever possible.
    • Placed 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.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Has the Awesome badge on the right side of the list heading,
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
  • Has an appropriate license.
    • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
    • If you use a license badge, it should be SVG, not PNG.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
  • Has consistent formatting and proper spelling/grammar.
    • Each link description starts with an uppercase character and ends with a period.
      Example: - [AVA](…) - JavaScript test runner.
    • Drop all the A / An prefixes in the descriptions.
    • Consistent naming. For example, Node.js, not NodeJS or node.js.
  • Doesn't include a Travis badge.
    You can still use Travis for list linting, but the badge has no value in the readme.
• Go to the top and read it again.

[0exbot]

@-legodude17 on 2017-04-19 16:22 says: Not followed:

• The repo should have the following GitHub topics set: awesome-list, awesome, list.
• Includes a succinct description of the project/theme at the top of the readme.
• Includes a project logo/illustration whenever possible.
• Has a Table of Contents section. (The Contents part should be a heading)
• Each link description starts with an uppercase character and ends with a period.
• Drop all the A / An prefixes in the descriptions.
• Has the Awesome badge on the right side of the list heading.