Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Update `who we are` in CONTRIBUTE.md
See original GitHub issuehttps://github.com/devtools-html/perf.html/blob/master/CONTRIBUTING.md#who-we-are
With the re-org, it might be a good time to update the CONTRIBUTING.md.
@julienw @gregtatum @mstange You probably know better about the how and able to provide more information here? 😃
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
docs/CONTRIBUTING.md at main - GitHub
We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You...
Read more >How to fill out the CONTRIBUTING.md template - IEEE GitLab
By convention, you should create a project named "About" in each IEEE SA OPEN group and subgroup, because this name forces that file...
Read more >How to Build a CONTRIBUTING.md
Reflect / Plan. Start by reflecting on what to include, and what to invite (in terms of contributions) in your CONTRIBUTING.md. See an...
Read more >Best practices to manage an open source project
The CONTRIBUTING.md file is a short guide to potential contributors on how they can contribute to your open source project. You can see...
Read more >Microsoft Learn documentation contributor guide overview
The guide describes how you can contribute to technical ... new article to Microsoft Learn or make updates to an existing published article....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe we should just remove the “Firefox DevTools” part, and directly use the roles instead.
Bryan should be replaced by @digitarald, and we need to add @brisad, and yourself @zoepage too of course.