Here's what's popular on GitHub today...
Trending repository
-
Updated
Jun 10, 2022 - JavaScript
The Download
On this episode of The Download, Christina is on location at RenderATL, but is still here to offer the latest developer news.
Popular topic
Trending repository
-
Updated
Jun 10, 2022 - Python
Trending repository
-
Updated
Jun 10, 2022 - Python
Upcoming event recommended by GitHub
Security at the Speed of GitHub
June 29, 2022 • Online
Trending repository
- Base README.md
- Quizzes
- Introduction base README
- Defining Data Science README
- Defining Data Science assignment
- Ethics README
- Ethics assignment
- Defining Data README
- Defining Data assignment
- Stats and Probability README
- Stats and Probability assignment
- Working with Data base README
- Rel
Trending repository
-
Updated
Jun 7, 2022 - Jupyter Notebook
Collection recommended by GitHub
Game Engines
Frameworks for building games across multiple platforms.
App recommended by GitHub
GuardRails
GuardRails scans new code changes as they occur in your repositories. For pull requests, we will post comments whenever security issues are detected. For branches, you will be able to see reports in your dashboard.
Trending repository
-
Updated
Jun 6, 2022 - Shell
Trending repository
-
Updated
Jun 10, 2022 - C++
Trending repository
-
Updated
Jun 8, 2022 - Python
Trending repository
-
Updated
Jun 10, 2022 - JavaScript
Trending repository
Is your feature request related to a problem?
I wanted to create an entity that is only shown to one player, but I can still change and resend. Unfortunately, the only way to do that is to manually run Entity#hideEntity on every player on the server, and any that log on after the entity is spawned.
Describe the solution you'd like.
I would like there to be a Entity#hideEntityByDefault w
Trending repository
Trending repository
-
Updated
Jun 10, 2022 - Python
Trending repository
-
Updated
Jun 1, 2022
Trending repository
-
Updated
Jun 8, 2022
Trending repository
-
Updated
Jun 10, 2022
Trending repository
Feature request
Place the access_log and error_log directives inside the main server block instead of http block.
Feature description
Disable access_log at http block:
File: /etc/nginx/nginx.conf
# ...
http {
# ...
access_log off;
# ...
}
# ...Enable per site access_log and error_log at main server block:
File: /etc/nginx/
Trending repository
-
Updated
Jun 10, 2022 - Python
Trending repository
-
Updated
Jun 9, 2022 - TypeScript
Trending repository
Trending repository
-
Updated
Jun 10, 2022 - C++
Trending repository
Prerequisites
- I have written a descriptive issue title
- I have searched existing issues to ensure the issue has not already been raised
Issue
npx jest __tests__/get.test.js -t "GET Index"
console.warn
strict mode: use allowUnionTypes to allow union type keyword at "#/properties/image" (strictTypes)
at checkStrictMode (node_modules/@fastify/ajv-compiler/
Trending repository
Is there an existing issue for this?
- I have searched the existing issues
Describe the problem
The current Build.yaml workflow is specific to building and testing the app module, however, there are more than 1 apps in the project.
Describe the solution
An additional build/test workflow should be added to also build/test app-nia-catalog
Additional context
N/A
Trending repository
Is your feature request related to a problem? Please describe.
As I understand, ruler now is not adding the x-org-scopeid header to the alertmanager API calls, when it sends an alert. This would be nice if someone also uses Cortex with a tenant-aware alertmanager setup.
Describe the solution you'd like
Add the tenant ID of the tenant, on which ruler executes the rules. This would also
Trending repository
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my [Ory Cl
App recommended by GitHub
Check Run Reporter
Check Run Reporter takes your JUnit, Checkstyle, and other structured reports and presents their results to you right in the GitHub UI. No more need to dig through your pages of CI logs to find out why your build failed.


