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.

Sign up for GitHub

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

Feature gh pages 2.4 improve mtl repo #435

Merged
merged 2 commits into from
Jan 12, 2024
Merged

Feature gh pages 2.4 improve mtl repo #435

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cc5e2b9
Removed prior pull request instructions (replaced with new)
ljmoody Jan 10, 2024
c33effc
Corrected linter action errors, 2 lines.
ljmoody Jan 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 2 additions & 16 deletions 2.0_introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ This manual is created using GitHub Pages (gh-pages). GitHub Pages is a web host

b. In the “Find or create a branch…” field, type in the name of this new branch using this naming convention: feature-gh-pages_(chapter #)_(title of chapter).
- Example: feature-gh-pages_chapter_7.0_mtl_technical_manual_facilitator
- **Note:** Typing “feature-“ at the beginning of the branch name will cause linter cactions to fire when committing the file (including checks for Markdown editorial rules, broken links, APA style adherence, and spelling).
- **Note:** Typing “feature-“ at the beginning of the branch name will cause linter actions to fire when committing the file (including checks for Markdown editorial rules, broken links, APA style adherence, and spelling).
- Congratulations! You’ve just made your own feature branch, where you can make your modifications, additions, and deletions.

#### Edit an Existing Markdown (.md) File
Expand Down Expand Up @@ -138,20 +138,6 @@ Once you are finished committing changes to an existing file or have created a n
- As you scroll down, you can see red and green highlighted information; red = deletions, green = additions.
5. Click the green Create pull request button.
6. A review page will appear where you can:
- Add a short summary of the changes between your feature branch and the repo’s base branch.
- Add a short summary of the changes between your feature branch and the repository's base branch.
- Review the changes made by commits.
- Add Pipelines, Reviewer/s, Assignee/s (usually you, the one making changes), Label/s, Project/s, Milestone/s, and Estimate (story points).

---
**prior instructions:**
1. Navigate to https://mtl.how via your browser.
2. *Switch from the Master branch to the QA branch - *Need a free GitHub account to contribute
3. Create a feature branch via a pull request from the qa branch
4. Edit markdown (.md) file on GitHub.
5. Conduct quality assurance (QA) on QA using GitHub Actions.
6. Merge your feature pull request into QA.
7. Create a pull request from QA to master and assign PROD QA reviewer on the right hand side.
8. The PROD QA reviewer will make a final review, ask any questions, and merge the PR into master.

**PROD QA reviewers DO NOT delete the QA branch** when merging QA pull requests to master.

Loading