Github Issues
Where it sits
Jobs that need it
- DevOps Engineercorelevel 3
- Android Developersupportinglevel 3
- Backend Developer (ASP.NET Core)supportinglevel 3
- Backend Developer (Go)supportinglevel 3
- Backend Developer (Java, Spring Boot)supportinglevel 3
- Backend Developer (Node.js)supportinglevel 3
- Backend Developer (Python)supportinglevel 3
- Flutter Developersupportinglevel 3
- Frontend Developer (Angular)supportinglevel 3
- Frontend Developer (React)supportinglevel 3
- Frontend Developer (Vue)supportinglevel 3
- Full Stack Developer (Java + React)supportinglevel 3
- Full Stack Developer (MEAN)supportinglevel 3
- Full Stack Developer (MERN)supportinglevel 3
- Full Stack Developer (Python + React)supportinglevel 3
- iOS Developersupportinglevel 3
- React Native Developersupportinglevel 3
What level 3 (Working) means
Uses it independently on the job. Level 4 (Strong): handles hard cases, reviews others.
Github Issues: common questions
What is Github Issues?
Github Issues is a skill in git-github, needed by 17 roles on BootSelf.
Which jobs need Github Issues?
DevOps Engineer, Android Developer, Backend Developer (ASP.NET Core), Backend Developer (Go), Backend Developer (Java, Spring Boot), and 12 more. Most ask for level 3 (Working): uses it independently on the job.
What should I learn before Github Issues?
Starting with GitHub, Introduction to GitHub actions.
How long does it take to learn Github Issues?
The starting lesson, Github Issues, takes about 7 minutes. Reaching the level a job asks for takes practice on top: BootSelf measures where you are and plans the rest.
How do I practise Github Issues?
Check your readiness for free, then BootSelf builds a route and short daily learning loops: a little theory, checks on what you get wrong, then a small program.