Skip to content

Join GitHub (or sign in) to find projects, people, and topics catered to your interests.

Here's what's popular on GitHub today...

JSON logo
Popular topic
JSON (JavaScript Object Notation) allows for easy interchange of data, often between a program and a database.
Trending repository
bartlomieju
bartlomieju commented Apr 16, 2020

To have Deno namespace in the worker, we'll want to provide a map of permissions worker should have. Worker's set of permissions mustn't escalate permissions of parent worker/Deno process.

To achieve that a method called fork should be added to DenoPermissions struct. fork would take as many parameters as there are fields on DenoPermissions and return new DenoPermissions instance a

Capture the Flag
Upcoming event recommended by GitHub
May
6

Capture the Flag

May 06, 2020 - June 12, 2020 • Online

The GitHub Security Lab CTF is a contest where participants are challenged to find a security bug (the flag) in real code.
web-vitals-extension
Trending repository
addyosmani
addyosmani commented May 2, 2020

The current badge overlay close button will remove the badge from the page, but will not persist the badge closure during your session. This might be surprising to developers (e.g I see my metrics -> close badge -> CLS wasn't final and just updated -> whoops here's the badge again).

Few options....

  1. Clicking close will be the same as disabling the overlay for the particular tab (i.e we upd
App recommended by GitHub

GitKraken Glo Boards

Sync GitHub Issues with Glo Boards to visualize your workflow

Glo Boards sync in real-time with GitHub Issues so changes made in either system are immediately reflected in the other. If some team members are using either Glo or GitHub exclusively, important information is still shared seamlessly.

Benefits of using Glo Boards with GitHub:

  • Sync GitHub Issues, assignees, descriptions, comments and labels in real-time across systems
  • Create different workflows and labels for each board
Trending repository
Trending repository
thernstig
thernstig commented Apr 29, 2020

Currently the bug report template requires these fields:

**Context:**
- Playwright Version: [what Playwright version do you use?]
- Operating System: [e.g. Windows, Linux or Mac]
- Node version: [e.g. 10.12, 10.14]
- Browser: [e.g. All, Chromium, Firefox, WebKit]
- Extra: [any specific details about your environment]

If you start using https://github.com/tabrindle/envinfo yo

Trending repository
njacharya
njacharya commented Aug 16, 2019

A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

App recommended by GitHub

Coveralls

Coveralls.io: Deliver Better Code

We help you deliver code confidently by showing which parts of your code aren’t covered by your test suite.

Eliminate Tech Debt

Maintaining a well-tested codebase is mission-critical, but figuring out where your tests are lacking can be painful. You're already running your tests on a continuous integration server, let it do the heavy lifting. Coveralls works with your CI to sift through coverage data to find gaps you didn't know you had.

You can’t perform that action at this time.