Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Updated list numbering #32991

Merged
merged 4 commits into from
Mar 3, 2022
Merged

docs: Updated list numbering #32991

merged 4 commits into from
Mar 3, 2022

Conversation

alvinphilips
Copy link
Contributor

The steps on the section to Package and Distribute an Application using Electron Forge had incorrect numbering

Description of Change

Checklist

  • relevant documentation is changed or added

Release Notes

Notes: none

The steps to package and distribute an application using electron had incorrect numbering
@welcome
Copy link

welcome bot commented Feb 19, 2022

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

  • fix: don't overwrite prevent_default if default wasn't prevented
  • feat: add app.isPackaged() method
  • docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

  • Follow the JavaScript, C++, and Python coding style.
  • Run npm run lint locally to catch formatting errors earlier.
  • Document any user-facing changes you've made following the documentation styleguide.
  • Include tests when adding/changing behavior.
  • Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Feb 19, 2022
@Medialabster

This comment was marked as off-topic.

Copy link
Contributor

@jkleinsc jkleinsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @PolarVoid!

Copy link
Contributor

@jkleinsc jkleinsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like lint is failing on this change. Not sure why, but marking this as changes requested so that it doesn't accidentally get merged.

@jkleinsc
Copy link
Contributor

@PolarVoid lint is failing because the code blocks under each point need to be indented (see DavidAnson/markdownlint#226 for more details)

Eg the change needed to fix lint would be:

 1. Add Electron Forge as a development dependency of your app, and use its `import` command to set up
 Forge's scaffolding:

-```sh npm2yarn
-npm install --save-dev @electron-forge/cli
-npx electron-forge import
+    ```sh npm2yarn
+    npm install --save-dev @electron-forge/cli
+    npx electron-forge import

-✔ Checking your system
-✔ Initializing Git Repository
-✔ Writing modified package.json file
-✔ Installing dependencies
-✔ Writing modified package.json file
-✔ Fixing .gitignore
+    ✔ Checking your system
+    ✔ Initializing Git Repository
+    ✔ Writing modified package.json file
+    ✔ Installing dependencies
+    ✔ Writing modified package.json file
+    ✔ Fixing .gitignore

-We have ATTEMPTED to convert your app to be in a format that electron-forge understands.
+    We have ATTEMPTED to convert your app to be in a format that electron-forge understands.

-Thanks for using "electron-forge"!!!
-```
+    Thanks for using "electron-forge"!!!
+    ```

 2. Create a distributable using Forge's `make` command:

-```sh npm2yarn
-npm run make
-
-> my-electron-app@1.0.0 make /my-electron-app
-> electron-forge make
-
-✔ Checking your system
-✔ Resolving Forge Config
-We need to package your application before we can make it
-✔ Preparing to Package Application for arch: x64
-✔ Preparing native dependencies
-✔ Packaging Application
-Making for the following targets: zip
-✔ Making for target: zip - On platform: darwin - For arch: x64
-```
+    ```sh npm2yarn
+    npm run make
+
+    > my-electron-app@1.0.0 make /my-electron-app
+    > electron-forge make
+
+    ✔ Checking your system
+    ✔ Resolving Forge Config
+    We need to package your application before we can make it
+    ✔ Preparing to Package Application for arch: x64
+    ✔ Preparing native dependencies
+    ✔ Packaging Application
+    Making for the following targets: zip
+    ✔ Making for target: zip - On platform: darwin - For arch: x64
+    ```

 Electron Forge creates the `out` folder where your package will be located:

@alvinphilips
Copy link
Contributor Author

@jkleinsc Aah okay, I get what you mean. I figured it was something wrong with how it was formatted. I'll get on it and make the required changes.

Copy link
Contributor

@jkleinsc jkleinsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested this locally, and it looks like you need to indent the code blocks with 4 spaces to resolve the lint issue.

Comment on lines 466 to 480
```sh npm2yarn
npm install --save-dev @electron-forge/cli
npx electron-forge import

✔ Checking your system
✔ Initializing Git Repository
✔ Writing modified package.json file
✔ Installing dependencies
✔ Writing modified package.json file
✔ Fixing .gitignore

We have ATTEMPTED to convert your app to be in a format that electron-forge understands.
Thanks for using "electron-forge"!!!
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This block needs to be indented 2 more spaces to resolve the lint issue.

Comment on lines 484 to 508
```sh npm2yarn
npm run make

> my-electron-app@1.0.0 make /my-electron-app
> electron-forge make

✔ Checking your system
✔ Resolving Forge Config
We need to package your application before we can make it
✔ Preparing to Package Application for arch: x64
✔ Preparing native dependencies
✔ Packaging Application
Making for the following targets: zip
✔ Making for target: zip - On platform: darwin - For arch: x64
```

Electron Forge creates the `out` folder where your package will be located:

```plain
// Example for macOS
out/
├── out/make/zip/darwin/x64/my-electron-app-darwin-x64-1.0.0.zip
├── ...
└── out/my-electron-app-darwin-x64/my-electron-app.app/Contents/MacOS/my-electron-app
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This block needs to be indented 2 more spaces to resolve the lint issue.

@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Feb 26, 2022
@jkleinsc
Copy link
Contributor

jkleinsc commented Mar 3, 2022

Merging as CI failure unrelated to PR change.

@jkleinsc jkleinsc merged commit 41c81ed into electron:main Mar 3, 2022
6 checks passed
@welcome
Copy link

welcome bot commented Mar 3, 2022

Congrats on merging your first pull request! 🎉🎉🎉

@release-clerk
Copy link

release-clerk bot commented Mar 3, 2022

No Release Notes

@trop
Copy link
Contributor

trop bot commented Mar 3, 2022

I was unable to backport this PR to "14-x-y" cleanly;
you will need to perform this backport manually.

@trop
Copy link
Contributor

trop bot commented Mar 3, 2022

I was unable to backport this PR to "15-x-y" cleanly;
you will need to perform this backport manually.

@trop
Copy link
Contributor

trop bot commented Mar 3, 2022

I was unable to backport this PR to "16-x-y" cleanly;
you will need to perform this backport manually.

@trop trop bot removed the target/15-x-y label Mar 3, 2022
@trop
Copy link
Contributor

trop bot commented Mar 3, 2022

I have automatically backported this PR to "17-x-y", please check out #33146

@trop
Copy link
Contributor

trop bot commented Mar 3, 2022

I have automatically backported this PR to "18-x-y", please check out #33147

bavulapati pushed a commit to bavulapati/electron that referenced this pull request Apr 29, 2022
* docs: Updated list numbering

The steps to package and distribute an application using electron had incorrect numbering

* Indented text within ordered list sections

* Removed single space

* Fixed indentation
khalwa pushed a commit to solarwindscloud/electron that referenced this pull request Feb 22, 2023
* docs: Updated list numbering

The steps to package and distribute an application using electron had incorrect numbering

* Indented text within ordered list sections

* Removed single space

* Fixed indentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants