Skip to content

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

logto

Trending repository

🧑‍🚀 Logto helps you build the sign-in, auth, and user identity within minutes. We provide an OIDC-based identity service and the end-user experience with username, phone number, email, and social sign-in, with extendable multi-language support.

  • Updated Jul 20, 2022
  • TypeScript
GraphQL logo

Popular topic

GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data.

Trending repository

30 Minutes to Merge: Accelerate shipping with GitHub Projects

Upcoming event recommended by GitHub

Aug
24

30 Minutes to Merge: Accelerate shipping with GitHub Projects

August 24, 2022 • Online

Organizations today are under pressure to do more with less. That's why productivity is such an important issue. Jed Verity will show you how to use GitHub Projects to boost productivity in your organization.
Testspace.com screenshot

App recommended by GitHub

Testspace.com

Test Management software for DevOps

Testspace provides a dashboard for publishing test results from automation and a framework for implementing and executing manual tests using GitHub.

  • Publish large volumes of test results with a single command
  • Implement Manual tests using text files contained in a repository
  • Improve process with metrics, graphs, and analytics
  • Auto-detect Flaky tests
  • Exploratory support

LIVE DEMO

freqtrade

Trending repository

JhorAVi
JhorAVi commented Jul 13, 2022

Hi, I have a trailing_stop_loss exit with small loss of -0.42% probably due to slippage. The problem is the StopLossGuard caught it because it's still considered a stoploss exit even though loss is small. Is there a workaround so that StopLossGuard won't mind those micro losses? Or even better is a way to exclude trailing_stop_loss from StopLossGuard's radar?

Thanks for the help

Good first issue Stoploss

Trending repository

Trending repository

dominikbraun
dominikbraun commented Jul 17, 2022

At the moment, edges consist of a source vertex, a target vertex, and a weight. It would be great to have a label as well:

type Edge[T any] struct {
	Source T
	Target T
	Weight int
	Label string
}

Possible APIs

  1. One approach to provide an API for adding a label to an edge is to implement methods such as EdgeWithLabel and WeightedEdgeWithLabel. This is a very sim
enhancement help wanted good first issue
docs

Trending repository

vedantsinghania05
vedantsinghania05 commented Apr 8, 2022

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/get-started/quickstart/create-a-repo

What part(s) of the article would you like to see updated?

I think that in the notes section of this page, there should be

help wanted good first issue content get started

Trending repository

cryptk
cryptk commented Aug 26, 2021

Description

If creating multiple VPCs on the same account, and creating the same endpoint type in those VPCs, you receive the following error:

Error: multiple VPC Endpoint Services matched; use additional constraints to reduce matches to a single VPC Endpoint Service

Versions

  • Terraform: 0.15.5
  • Provider(s):
  • provider registry.terraform.io/hashic
Jira Software + GitHub screenshot

App recommended by GitHub

Jira Software + GitHub

The Jira and GitHub integration synchronizes development across tools and uses automation to remove manual steps and shorten delivery time.

By connecting your code in GitHub to your projects in Jira, your developers can focus less on updates and more on building great products. And with source code data flowing through Jira, the broader team can visualize deployment data in one place, extract key insights, and build powerful automations in Jira.