In order to certify that you've completed the prerequisites for the second Salesforce DX for ISVs Workshop, please complete the five steps as presented in this document.
โ ๏ธ IMPORTANT: You must complete the steps as presented in this document without taking shortcuts that might be apparent to experienced users. Completing the steps as presented will help to surface any technical issues with your local and/or GitHub account setup. Finding and fixing these issues ahead of time will help you get the most out of the workshop.
If you're not already logged in to GitHub, go to https://github.com/login and log in with the GitHub account that you plan on using with the Salesforce DX for ISVs Workshop.
After logging into GitHub, you will need to make a personal copy of the sfdx-isv/travel-expenses
repository by forking it.
To fork the sfdx-isv/travel-expenses
repository, follow these steps.
- Open your web browser to https://github.com/sfdx-isv/travel-expenses
- Click the Fork button at the top-right of the repository's page
Once the sfdx-isv/travel-expenses
repository has been forked, your screen will look similar to this:
- The URL will include your GitHub username after
github.com
and beforetravel-expenses
, indicating that the forked repository is now part of your account. - The title of the repository will also indicate that this repository belongs to your GitHub account, and that it was originally forked from the
sfdx-isv/travel-expenses
repo.
After forking the sfdx-isv/travel-expenses
repository, you must clone it to your local machine in order to add your information to the Prerequisite Certification table.
To clone your fork of the sfdx-isv/travel-expenses
repository, follow these steps.
- From the Code tab of your forked repository, click the Clone or Download button.
- Make sure that the Clone with HTTPS option is specified.
- Click the Copy to Clipboard
git clone PASTE_YOUR_GITHUB_URI_HERE my-travel-expenses-fork
- Type the
git clone
command at the command line.- IMPORTANT: Make sure to use the HTTPS URI of your forked repository in place of
PASTE_YOUR_GITHUB_URI_HERE
. - IMPORTANT: Remember to specify the local folder name
my-travel-expenses-fork
after your GitHub URI to ensure that your forked repository is cloned into a local folder using that name. - The screenshot shows the what this command and its results look like when used by the developer "Jessie Daniels".
- IMPORTANT: Make sure to use the HTTPS URI of your forked repository in place of
After cloning your forked repository, you will have a local copy of it on your local machine. From here you'll need to add your information to the file CERTIFICATION.md
before pushing your changes back into your forked repository on GitHub.
To do this, follow these steps.
- Using VS Code, open the folder containing your cloned repository (
my-travel-expenses-fork
). - In the VS Code Explorer, double-click on the file
CERTIFICATION.md
to open it. - Observe the last row of the markdown table (line 11).
- In the next step you will be editing this line.
- Substitute your name, GitHub username, and today's date for the values
**YOUR NAME HERE**
,**YOUR GITHUB USERNAME HERE**
, andDATE YOU ADDED YOUR NAME
.- IMPORTANT: Remember to save your changes to this file.
- Open the VS Code Developer Panel by pressing
CMD+J
(CTRL+J
on Windows) - Once the panel is open, click on the TERMINAL tab to get a CLI.
- Execute the command
git add -A
to stage your change - Execute the command
git status
to verify thatCERTIFICATION.md
is staged for commit. - Execute the command
git commit -m "Update CERTIFICATION.md - YOUR_FIRST_AND_LAST_NAME"
- IMPORTANT: Make sure that you substitute your own first and last name for
YOUR_FIRST_AND_LAST_NAME
.
- IMPORTANT: Make sure that you substitute your own first and last name for
- Execute the command
git status
- You should see that your local branch is ahead of
origin/master
by 1 commit.
- You should see that your local branch is ahead of
- Execute the command
git push origin master
- You should see output that is similar to the screenshot, below.
The final step in the Workshop Prerequisite Certification process is the creation of a pull request to merge the changes from your forked repository into the base sfdx-isv/travel-expenses repository.
To do this, follow these steps.
- Open the GitHub website and make sure that you are inside of your forked
travel-expenses
repository. - Open the Pull requests tab in your forked repository.
- Click the New pull request button to start the process of creating a new pull request.
- Clicking the New pull request button on the previous step opens the Compare Tool in the
sfdx-isv/travel-expenses
base repository. - Verify that you are comparing changes FROM your forked
travel-expenses
repository (on the right) TO the basesfdx-isv/travel-expenses
repository (on the left). - Near the bottom of the page, you'll see a list of files that are different between the forked and base repositories.
- You should see a message that you have 1 changed file,
- You should also be able to see the details of the change you made to
CERTIFICATION.md
.
- If everything looks right, click the Create pull request button.
- Add the subject
Prerequisite Certification - YOUR_FIRST_AND_LAST_NAME_HERE
. Make sure to replace the placeholder text with your actual first and last name. - Add a comment explaining that you are certifying your completion of the prerequisites for Salesforce DX for ISVs - Workshop Two.
- Click the Create pull request button.
- Make sure you're in the base repository,
sfdx-isv/travel-expenses
. - Open the Pull requests tab.
- Look for the Pull Request that you created (ie. the one that has a title with your name in it).