Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Open more actions menu

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
12 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

DevSecOps Workshops: Git & Github

This is a brief introduction to Git, Github, and Github Actions. For the workshop material, visit github.com/devopsies/search-engine-app.

What is Git?

Git is a software for tracking changes in any set of files, usually used for coordinating work among programmers collaboratively developing source code during software development. For more information, visit git-scm.com/doc.

What is Git?

Github is a provider of Internet hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features. For more information, visit docs.github.com/en/github.

What are Github Actions?

GitHub Actions connects all of your tools to automate every step of your development workflow, including and not limited to CI/CD pipelines/jobs. It is hosted on Github (no installation required, as opposed to Jenkins). For more information, visit docs.github.com/en/actions.

Start using Git, Github & Github Actions

In this workshop, we're going to pretend we're building a product in C++: our awesome search engine. First, fork this repository. Forking will create a copy of this repository under you Github account. Then clone the repository (the one you created when you forked) to create a local copy of it. When solving any of the following issues, start from your main branch, create and switch to a new local branch optimizing search or optimizing pipeline depending on the issue you're working on, then add and commit your changes locally, and finally push them to your forked repository on Github. Next, on Github, trigger a pull request (PR) in order to start merging you newly created branch in your forked repository, to our main branch in our original repository.

The following diagram shows the described workflow:

First issue

You're the developer. The product you're developing (the search engine) currently do not satisfy the requirements as it becomes very slow with a large amount of input. Refer to the issue at github.com/mdnfiras/devsecops-github-actions/issues/1 for more details. If you have any question regarding this task, you can leave a comment in that same issue.

Second issue

You're a DevOps engineer. The CI pipeline you've set up is slow. refer to the issue at github.com/mdnfiras/devsecops-github-actions/issues/3 for more details. If you have any question regarding this task, you can leave a comment in that same issue.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Morty Proxy This is a proxified and sanitized view of the page, visit original site.