In the setup guide, users may need more guidance on what SKU to select. From experience I know which VMs have GPUs, and how to request more quota if I find I can’t create a VM, but your repo users might not know those things. But even so, I'm unsure what type of VM to create, because at this point I know very little of CVBP e.g. whether there is any point having more than one GP
Lean Board is a collaborative whiteboard with sticky notes which seamlessly connects with your GitHub issue. Login with your GitHub account, create a board for an issue and a snapshot of your notes is embedded in the issue automatically.
This issue will use computer science algorithms as an example but the issue is not about that specific topic but rather the implementation of ANY "track".
In addition to the three skill based tiers there should be knowledge pursuit tracks allowing new learners to move through those tiers onto related app-projects. This differs from #34 by focusing on a self directed educational go
When I try to handle non-existing routes, I redirect them to 404 page. When scully handles navigation and tries to get content for it, it will try to load index.html from non-existing page instead of using the one from 404. I believe the same issue would exist with any kind of redirection, e.g. using guards would also lead to undesired behavior.
We added LinkParser in 3.0 to replace some functionality that people used IRouter for in the past. This is briefly mentioned in the 2.2->3.0 migration docs, but we should probably have a dedicated section for it.
It is not clear to me how i should practically note the copyright of a code part (for example 5 lines from a MIT project). Is it legally OK to just note the source, author and license in the commit message description or should it be in the header of the file or in the LICENSE file of the project?
When i copy whole files, the license header should not be r
This repository is primarily maintained by Omar Santos and includes thousands of resources related to ethical hacking / penetration testing, digital forensics and incident response (DFIR), vulnerability research, exploit development, reverse engineering, and more.