1. Using Trigger Framework by Kevin O'Hara
2. Using lighting Components by lightningstrike
3. Using Connected Api helper class by forcedotcom
4. Using Git Actions to deploy inspired by Salto

Basic Code Structure for any project

1. TriggerHandler class for creating trigger helpers

1. strike_lookup component for creating lookup fields no need to write all functinality just pass attributes
2. strike_modal component to use modal without banging head for modal css

1. TestDataFactory : test class data helper class

   a.getAdminUser() : returns system admin user

   b.getStandardUser() : returns standard user

   c.createContentVersion(Boolean isInsert) : return contentVersion

2. Log : loging helper class to unify loging to system

   a.exception(Exception ex),exception(Exception ex,String msg) : logs exception with error logging level and add exception data

   b.error(String msg) : logs message with error loging level

   c.warn(String msg) : logs message with warn loging level

   d.info(String msg) : logs message with info loging level

   e.debug(String msg) : logs message with debug loging level

3. UITheme : Get Users current displayed theam

   a.getTheme() : returns users current view state theme

1. ConnectApiHelper : helper class to post message to chattter

   a.createFeedItemInputFromBody(): add's text to exsisitng chatter message

1. Create a new PR with related components to deploy
2. On Create of PR,package check will occurs with production org

Apex::[LogTest]::Apex

Apex::[all]::Apex

1. On push comment add "[Deploy]" in comment to mark it as deployment

2. in case summary add Apex::[T]::Apex to run specific class during deployment

3. on successfully merge it will be deployed to production org

add git secrete variable

SFDX_PRODUCTION_URL

and value of it copy from running command

sfdx force:org:display --targetusername <orgname> --verbose

and copy Sfdx Auth Url