Skip to content

Commit 6f90d0e

Browse files
committed
chore(docs): move contribution information
1 parent 5b95c2c commit 6f90d0e

4 files changed

Lines changed: 10 additions & 11 deletions

File tree

README.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@
5353
<p>📌<strong>Tip:</strong> To link directly to a specific rule, use the full GitHub anchor link format. Example:</p>
5454
<p><em><a href="https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context">https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context</a></em></p>
5555

56-
> Want to code a new rule? → See [How to Write a Rule](docs/write-a-rule.md)
56+
> Want to help improve this project? See our [Contributing Guidelines](CONTRIBUTING.md)
5757
5858
<!-- START GENERATED_RULES -->
5959
### Problems
@@ -628,4 +628,3 @@ For more on Programmatic API, types, and advanced usage of `@flow-scanner/lightn
628628
```
629629
This creates UMD at `dist/lightning-flow-scanner-core.umd.js`.
630630

631-
**Want to help improve Lightning Flow Scanner? See our [Contributing Guidelines](CONTRIBUTING.md)**

packages/action/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ Scan all flows on every push to selected branches.
133133
<p>📌<strong>Tip:</strong> To link directly to a specific rule, use the full GitHub anchor link format. Example:</p>
134134
<p><em><a href="https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context">https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context</a></em></p>
135135
136-
> Want to code a new rule? → See [How to Write a Rule](https://github.com/Flow-Scanner/lightning-flow-scanner/blob/main/docs/write-a-rule.md)
136+
> Want to help improve this project? See our [Contributing Guidelines](https://github.com/Flow-Scanner/lightning-flow-scanner?tab=contributing-ov-file)
137137
138138
<!-- START GENERATED_RULES -->
139139
### Problems
@@ -209,6 +209,7 @@ After-save Flows that update the same record can trigger recursion, causing unin
209209
**Severity:** 🟡 *Warning*
210210
211211
212+
212213
### Suggestions
213214
214215
### Action Call In A Loop
@@ -282,6 +283,7 @@ Loop elements that perform direct Assignments on each item can slow down Flows.
282283
**Severity:** 🔵 *Note*
283284
284285
286+
285287
### Layout
286288
287289
### Flow Naming Convention
@@ -574,5 +576,3 @@ Then test with:
574576
```bash
575577
act workflow_dispatch --secret-file .secrets
576578
```
577-
578-
**Want to help improve [Lightning Flow Scanner](https://github.com/Flow-Scanner)? See our [Contributing Guidelines](https://github.com/Flow-Scanner/lightning-flow-scanner-core/blob/main/CONTRIBUTING.md).**

packages/cli/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ sf flow:fix -d src/force-app # Fix flows in a specific directory
8181
<p>📌<strong>Tip:</strong> To link directly to a specific rule, use the full GitHub anchor link format. Example:</p>
8282
<p><em><a href="https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context">https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context</a></em></p>
8383

84-
> Want to code a new rule? → See [How to Write a Rule](https://github.com/Flow-Scanner/lightning-flow-scanner/blob/main/docs/write-a-rule.md)
84+
> Want to help improve this project? See our [Contributing Guidelines](https://github.com/Flow-Scanner/lightning-flow-scanner?tab=contributing-ov-file)
8585
8686
<!-- START GENERATED_RULES -->
8787
### Problems
@@ -157,6 +157,7 @@ After-save Flows that update the same record can trigger recursion, causing unin
157157
**Severity:** 🟡 *Warning*
158158

159159

160+
160161
### Suggestions
161162

162163
### Action Call In A Loop
@@ -230,6 +231,7 @@ Loop elements that perform direct Assignments on each item can slow down Flows.
230231
**Severity:** 🔵 *Note*
231232

232233

234+
233235
### Layout
234236

235237
### Flow Naming Convention
@@ -536,5 +538,3 @@ npm install -g lightning-flow-scanner
536538
```bash
537539
sf plugins link packages/cli
538540
```
539-
540-
<p><strong>Want to help improve Lightning Flow Scanner? See our <a href="https://github.com/Flow-Scanner/lightning-flow-scanner?tab=contributing-ov-file">Contributing Guidelines</a></strong></p>

packages/vsx/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Lightning Flow Scanner VSX is plug-and-play. Open any project with flows and use
6464
<p>📌<strong>Tip:</strong> To link directly to a specific rule, use the full GitHub anchor link format. Example:</p>
6565
<p><em><a href="https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context">https://flow-scanner.github.io/lightning-flow-scanner/#unsafe-running-context</a></em></p>
6666

67-
> Want to code a new rule? → See [How to Write a Rule](https://github.com/Flow-Scanner/lightning-flow-scanner/blob/main/docs/write-a-rule.md)
67+
> Want to help improve this project? See our [Contributing Guidelines](https://github.com/Flow-Scanner/lightning-flow-scanner?tab=contributing-ov-file)
6868
6969
<!-- START GENERATED_RULES -->
7070
### Problems
@@ -140,6 +140,7 @@ After-save Flows that update the same record can trigger recursion, causing unin
140140
**Severity:** 🟡 *Warning*
141141

142142

143+
143144
### Suggestions
144145

145146
### Action Call In A Loop
@@ -213,6 +214,7 @@ Loop elements that perform direct Assignments on each item can slow down Flows.
213214
**Severity:** 🔵 *Note*
214215

215216

217+
216218
### Layout
217219

218220
### Flow Naming Convention
@@ -510,5 +512,3 @@ code --install-extension ForceConfigControl.lightning-flow-scanner-vsx
510512
```bash
511513
pnpm test:vsx
512514
```
513-
514-
<p><strong>Want to help improve Lightning Flow Scanner? See our <a href="https://github.com/Flow-Scanner/lightning-flow-scanner?tab=contributing-ov-file">Contributing Guidelines</a></strong></p>

0 commit comments

Comments
 (0)