[PR #837] [CLOSED] Add Tech Events #6446

New Issue

GiteaMirror · 2026-04-17T11:33:04-05:00

GiteaMirror commented

2026-04-17 11:33:04 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/837
Author: @zaiste
Created: 12/6/2016
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (1)

e61f276 Add Tech Events

📊 Changes

1 file changed (+8 additions, -0 deletions)

View changed files

📝 readme.md (+8 -0)

📄 Description

https://github.com/eventil/awesome-tech-events
https://github.com/eventil/awesome-javascript-conferences

It's a new section for aggregating all tech events with a distinction between conferences and smaller events.

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

Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.

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 (not the list itself), and should be added at the bottom of the appropriate category.
The list I added
- has been around for at least 30 days,
- is the result of hard work and is the best I could possibly produce,
- is a non-generated Markdown file in a GitHub repo,
- is not a duplicate,
- includes a succinct description of the project/theme at the top (example),
- includes a project logo/illustration (whenever possible) at the top right of the readme (example). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.),
- only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),
- contains the awesome badge on the right side of the list heading,
- has a Table of Contents section named Contents as the first section,
- has an appropriate license (Meaning 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,
- doesn't include a Travis badge,
- has been checked for inconsistent formatting, spelling, and grammar:
  - Each link description starts with an uppercase character and ends with a period.
  - Drop all the A / An prefixes in the descriptions.
  - Consistent naming. For example, Node.js, not NodeJS or node.js.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/837 **Author:** [@zaiste](https://github.com/zaiste) **Created:** 12/6/2016 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`e61f276`](https://github.com/sindresorhus/awesome/commit/e61f276a9929b58937ff8cd73671275619eb8548) Add Tech Events ### 📊 Changes **1 file changed** (+8 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+8 -0) </details> ### 📄 Description https://github.com/eventil/awesome-tech-events https://github.com/eventil/awesome-javascript-conferences It's a new section for aggregating all tech events with a distinction between conferences and smaller events. # By submitting this pull request I confirm I've read and complied with the below requirements. Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things. - I have read and understood the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) and the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md). - 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 (not the list itself), and should be added at the bottom of the appropriate category. - The list I added - **has been around for at least 30 days,** - is the result of hard work and is the best I could possibly produce, - is a non-generated Markdown file in a GitHub repo, - is not a duplicate, - includes a succinct description of the project/theme at the top ([example](https://github.com/willempienaar/awesome-quantified-self)), - includes a project logo/illustration (whenever possible) at the top right of the readme ([example](https://github.com/sindresorhus/awesome-electron)). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.), - only has awesome items **with descriptions** *(Awesome lists are curations of the best, not of everything)*, - contains the [awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge) on the right side of the list heading, - has a Table of Contents section **named `Contents`** as the first section, - has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license) *(Meaning 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](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines), - doesn't include a Travis badge, - has been checked for inconsistent formatting, spelling, and grammar: - Each link description starts with an uppercase character and ends with a period. - Drop all the `A` / `An` prefixes in the descriptions. - Consistent naming. For example, `Node.js`, not `NodeJS` or `node.js`. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-17 11:33:04 -05:00

GiteaMirror closed this issue

2026-04-17 11:33:04 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#6446