Skip to content

Commit 29f6a81

Browse files
committed
remove outdated video
1 parent 5d0f9ef commit 29f6a81

File tree

4 files changed

+2
-54
lines changed

4 files changed

+2
-54
lines changed

.circleci/config.yml

Lines changed: 0 additions & 49 deletions
This file was deleted.

.circleci/note.txt

Lines changed: 0 additions & 2 deletions
This file was deleted.

CONTRIBUTING.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,3 @@
11
# Guide to Contributing
2-
Delete the contents of this file and replace with the contents of a proper guide to contributing to this project, as described in the [instructions](./instructions.md)
2+
3+
Delete the contents of this file and replace with the contents of a proper guide to contributing to this project, as described in the [instructions](./instructions-0c-project-setup#contributingmd)

instructions-0c-project-setup.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,8 +129,6 @@ Once a particular sprint has begun, all issues representing tasks that have been
129129

130130
Each team must create a Task Board for each of the four Sprints following [these setup instructions](https://knowledge.kitchen/content/courses/agile-development-and-devops/scrum/github-project-management/).
131131

132-
View a [video overview of setting up a Task Board on GitHub](https://youtu.be/Qasz5fhxIqE).
133-
134132
### Git/GitHub workflow
135133

136134
When in development, teams are expected to follow the [feature branch workflow](https://knowledge.kitchen/content/courses/agile-development-and-devops/slides/feature-branch-workflow/), where all changes are made in branches, peer reviews are done via pull requests, and approved changes are merged into the `main` branch, which is always in a deployable state.

0 commit comments

Comments
 (0)