e8517065d1
* docs: add links to the issue tracker Adding links to the issue tracker for existing issues and submission of new issues makes it easier to do what is otherwise well described in the issues doc. There are direct links to the issue tracker in other introductory docs, so I see no reason not to have them here, to facilitate access. * docs: update issues TOC * Changes recommended by malept |
||
|---|---|---|
| .. | ||
| atom-shell-vs-node-webkit.md | ||
| azure-vm-setup.md | ||
| build-instructions-gn.md | ||
| build-instructions-linux.md | ||
| build-instructions-macos.md | ||
| build-instructions-windows.md | ||
| build-system-overview.md | ||
| chromium-development.md | ||
| clang-format.md | ||
| coding-style.md | ||
| debug-instructions-windows.md | ||
| debugging-instructions-macos-xcode.md | ||
| debugging-instructions-macos.md | ||
| goma.md | ||
| issues.md | ||
| patches.md | ||
| pull-requests.md | ||
| README.md | ||
| setting-up-symbol-server.md | ||
| source-code-directory-structure.md | ||
| testing.md | ||
| upgrading-node.md | ||
| v8-development.md | ||
Developing Electron
These guides are intended for people working on the Electron project itself. For guides on Electron app development, see /docs/README.md.
- Code of Conduct
- Contributing to Electron
- Issues
- Pull Requests
- Documentation Styleguide
- Source Code Directory Structure
- Coding Style
- Using clang-format on C++ Code
- Build System Overview
- Build Instructions (macOS)
- Build Instructions (Windows)
- Build Instructions (Linux)
- Chromium Development
- V8 Development
- Testing
- Debugging on Windows
- Debugging on macOS
- Setting Up Symbol Server in Debugger
- Patches
- Upgrading Node