ci: ignore PR automerge failure

.github/workflows/packaging.yml

@@ -95,6 +95,7 @@ jobs:
 
             # Approve and mark PR for auto merge
             - name: 'Approve and mark PR for auto merge'
+              continue-on-error: true
               run: |
                   gh pr review --approve "$PR_NUMBER"
                   gh pr merge --auto --squash "$PR_NUMBER"

force-app/main/default/staticresources/documentation/AccountServiceLayer.md

@@ -21,7 +21,8 @@ by the AccountTriggerHandler
 ## Methods
 ### `public static void justWriteALogStatement(String toLog)`
 
-Method exists to demonstrate what it might look like to  call a service layer method from a trigger handler.
+Method exists to demonstrate what it might look like to
+ call a service layer method from a trigger handler.
 
 #### Parameters
 
@@ -35,11 +36,17 @@ AccountServiceLayer.justWriteALogStatement('Hello World');
 ```
 
 
-### `public static void changeShippingStreet(List<Account> accounts, System accessLevel)`
+### `public static void changeShippingStreet(List<Account> accounts, System.AccessLevel accessLevel)`
 
 `SUPPRESSWARNINGS`
 
-Changes the account's Shipping Street field to a hardcoded value. You should do this kind of work in a before trigger, but this is a demo. Note: This method contains a false-positive PMD viloation around not checking FLS/CRUD before doing DML. This is because PMD is unaware of what the CanTheUser call right before it is doing - namely checking CRUD.
+Changes the account's Shipping Street field to a hardcoded
+value. You should do this kind of work in a before trigger, but this is a
+demo.
+
+Note: This method contains a false-positive PMD viloation around not
+checking FLS/CRUD before doing DML. This is because PMD is unaware of
+what the CanTheUser call right before it is doing - namely checking CRUD.
 
 #### Parameters
 
@@ -57,7 +64,8 @@ System.debug([SELECT Name, ShippingStreet FROM Account WHERE Id in : accounts]);
 
 ### `public static List<Account> incrementCounterInDescription(List<Account> incomingAccounts, Boolean save)`
 
-Increments a counter stored in the Description field.  Demonstration method of the kind of work a service layer may do.
+Increments a counter stored in the Description field.
+ Demonstration method of the kind of work a service layer may do.
 
 #### Parameters
 
@@ -84,7 +92,9 @@ System.debug([SELECT Name, Description FROM Account WHERE Id in : accounts]);
 
 `TESTVISIBLE`
 
-Updates a list of accounts if the user has access to update  the Account Object. Demonstrates simple usage of  Security.stripInacessible(), and DML with a try/catch block.
+Updates a list of accounts if the user has access to update
+ the Account Object. Demonstrates simple usage of
+ Security.stripInacessible(), and DML with a try/catch block.
 
 #### Parameters
 

force-app/main/default/staticresources/documentation/AccountShippingCountryComparator.md

@@ -13,9 +13,10 @@ In this example we show how to sort all the accounts by their country names in a
 
 No param constructor. Assigns sort order as ascending by default
 
-### `public AccountShippingCountryComparator(AccountShippingCountryComparator order)`
+### `public AccountShippingCountryComparator(AccountShippingCountryComparator.SortOrder order)`
 
-Constructor accepting sort order as ascending/descending. Use this constructor to *control* the sort order.
+Constructor accepting sort order as ascending/descending. Use
+this constructor to *control* the sort order.
 
 #### Parameters
 

force-app/main/default/staticresources/documentation/AccountTriggerHandler.md

@@ -22,7 +22,8 @@ AccountTriggerHandler
 ## Constructors
 ### `public AccountTriggerHandler()`
 
-Constructor that sets class variables based on Trigger context vars
+Constructor that sets class variables based on Trigger
+context vars
 
 ---
 ## Fields
@@ -52,7 +53,8 @@ Constructor that sets class variables based on Trigger context vars
 ## Methods
 ### `public override void beforeInsert()`
 
-Before Insert context method. Called automatically by the trigger framework this class extends.
+Before Insert context method. Called automatically by the
+trigger framework this class extends.
 
 #### Example
 ```apex
@@ -65,7 +67,8 @@ insert accounts;
 
 ### `public override void afterInsert()`
 
-after insert context method. Called automatically by the trigger framework this class extends
+after insert context method. Called automatically by the
+trigger framework this class extends
 
 #### Example
 ```apex
@@ -78,7 +81,8 @@ insert accounts;
 
 ### `public override void beforeUpdate()`
 
-before update context method. Called automatically by the trigger framework this class extends
+before update context method. Called automatically by the
+trigger framework this class extends
 
 #### Example
 ```apex
@@ -95,7 +99,14 @@ update accounts;
 
 `SUPPRESSWARNINGS`
 
-after update context method. Called automatically by the trigger framework this class extends Note: this method contains a PMD false-positive report about CRUD checking before insert. However, trigger code is run in system mode, regardless of users, so it doesn't make sense to check for Account and Task permissions. This code is therefore only safe to execute in the context of a trigger.
+after update context method. Called automatically by the
+trigger framework this class extends
+
+Note: this method contains a PMD false-positive report about CRUD
+checking before insert. However, trigger code is run in system mode,
+regardless of users, so it doesn't make sense to check for Account and
+Task permissions. This code is therefore only safe to execute in the
+context of a trigger.
 
 #### Example
 ```apex
@@ -112,7 +123,14 @@ update accounts;
 
 `SUPPRESSWARNINGS`
 
-before delete context method. Called automatically by the trigger framework this class extends Note: this method contains a PMD false-positive report about CRUD checking before insert. However, trigger code is run in system mode, regardless of users, so it doesn't make sense to check for Account and Task permissions. This code is therefore only safe to execute in the context of a trigger.
+before delete context method. Called automatically by the
+trigger framework this class extends
+
+Note: this method contains a PMD false-positive report about CRUD
+checking before insert. However, trigger code is run in system mode,
+regardless of users, so it doesn't make sense to check for Account and
+Task permissions. This code is therefore only safe to execute in the
+context of a trigger.
 
 #### Example
 ```apex
@@ -127,7 +145,14 @@ delete accounts;
 
 `SUPPRESSWARNINGS`
 
-after delete context method. Called automatically by the trigger framework this class extends Note: this method contains a PMD false-positive report about CRUD checking before insert. However, trigger code is run in system mode, regardless of users, so it doesn't make sense to check for Account and Task permissions. This code is therefore only safe to execute in the context of a trigger.
+after delete context method. Called automatically by the
+trigger framework this class extends
+
+Note: this method contains a PMD false-positive report about CRUD
+checking before insert. However, trigger code is run in system mode,
+regardless of users, so it doesn't make sense to check for Account and
+Task permissions. This code is therefore only safe to execute in the
+context of a trigger.
 
 #### Example
 ```apex
@@ -142,7 +167,14 @@ delete accounts;
 
 `SUPPRESSWARNINGS`
 
-after undelete context method. Called automatically by the trigger framework this class extends Note: this method contains a PMD false-positive report about CRUD checking before insert. However, trigger code is run in system mode, regardless of users, so it doesn't make sense to check for Account and Task permissions. This code is therefore only safe to execute in the context of a trigger.
+after undelete context method. Called automatically by the
+trigger framework this class extends
+
+Note: this method contains a PMD false-positive report about CRUD
+checking before insert. However, trigger code is run in system mode,
+regardless of users, so it doesn't make sense to check for Account and
+Task permissions. This code is therefore only safe to execute in the
+context of a trigger.
 
 #### Example
 ```apex
@@ -159,7 +191,9 @@ undelete accounts;
 *Inherited*
 
 
-This is main brokering method that is called by the trigger. It's responsible for determining the proper context, and calling the correct method
+This is main brokering method that is called by the trigger.
+It's responsible for determining the proper context, and calling the
+correct method
 
 #### Example
 ```apex
@@ -172,7 +206,9 @@ AccountTriggerHandler.run();
 *Inherited*
 
 
-Allows developers to prevent trigger loops, or allow a limited number of them by setting the maximum number of times this trigger is called.
+Allows developers to prevent trigger loops, or allow
+a limited number of them by setting the maximum number of times
+this trigger is called.
 
 #### Parameters
 
@@ -206,7 +242,8 @@ this.clearMaxLoopCount();
 *Inherited*
 
 
-Allows developers to conditionally bypass (disable) other triggers that *also* implement this triggerHandler
+Allows developers to conditionally bypass (disable)
+other triggers that *also* implement this triggerHandler
 
 #### Parameters
 
@@ -225,7 +262,8 @@ TriggerHandler.bypass('AccountTriggerHandler');
 *Inherited*
 
 
-Removes a given trigger handler class name from the list of bypassed trigger handlers.
+Removes a given trigger handler class name from
+the list of bypassed trigger handlers.
 
 #### Parameters
 
@@ -244,7 +282,8 @@ TriggerHandler.clearBypass('AccountTriggerHandler');
 *Inherited*
 
 
-Allows developers to check whether a given trigger handler class is currently bypassed.
+Allows developers to check whether a given trigger
+handler class is currently bypassed.
 
 #### Parameters
 

force-app/main/default/staticresources/documentation/ApexClassUtilities.md

@@ -16,7 +16,8 @@ in an org.
 ## Methods
 ### `public static String getGroupFromClassBody(ApexClass klass)`
 
-Extracts the `@group` annotation from a class' body. Also demonstrates the use of Regex matchers in Apex.
+Extracts the `@group` annotation from a class' body.
+Also demonstrates the use of Regex matchers in Apex.
 
 #### Parameters
 
@@ -39,7 +40,8 @@ System.debug(ApexClassUtilities.getGroupFromClassBody(klass));
 
 ### `public static List<String> getRelatedClassesFromClassBody(ApexClass klass)`
 
-Extracts the `@see` annotations from a class' body. Also demonstrates the use of Regex matchers in Apex.
+Extracts the `@see` annotations from a class' body.
+Also demonstrates the use of Regex matchers in Apex.
 
 #### Parameters