DX (Developer Experience) intro

DX - Developer Experience. This tutorial introduces some of the features in the GitHub eco-system that will make your team go faster - in a very DevOpsy way. Catering for the Developer Experience

👉 Create your own copy of this repo 👈

Use this repo as a template - not a fork¹

Code >> Use this template >> Create new repository

👉 Work those issues 👈

There's a automated GitHub Actions workflow that starts immidately when you generate your repository - it copies the template issues over to your own repo - It may take 15-20 seconds to finish - You can monitor it in the Actions tab - of your own newly created repo.

Continue there - in your own repo. Go to the "issues" tab in your own copy and simply work the issues.

👉 If you need help 👈

The discussions are enabled on the template repo (your source). If you need help, if you want to suggets improvements or if you have an urge to contribute to this tutorial - simply make a statement in the discussions. Feel free to mention me; @lakruzz.

Footnotes

1. template and fork are two different concepts although somewhat similar; Forks clone all branches and all history and they maintain a relation to the repo they forked off, allowing them to push and pull back and forth. Templates on the other side are are completely detached from the source and they only take the HEAD commit on the default branch; it's a fresh start. ↩