What best describes Markdown?
Markdown is a lightweight markup language with plain-text formatting syntax. It is designed to be easy to write and read in its raw form, and it can be converted into HTML and other formats. Markdown is commonly used for formatting readme files, writing messages in online discussion forums, and creating rich text documents.
Markup Language:
Option A is correct because Markdown is indeed a markup language. It is not a programming language, scripting language, version control system, or containerization solution.
Incorrect Options:
Option B is incorrect because Markdown is not a programming language; it does not involve control structures or variables.
Option C is incorrect because Markdown is not used for scripting or automation.
Option D is incorrect because Markdown does not manage version control.
Option E is incorrect because Markdown is not related to containerization technologies like Docker.
Which of the following can be performed within GitHub Mobile?
GitHub Mobile provides a streamlined experience for managing your GitHub notifications and participating in discussions, but it does not offer full functionality compared to the desktop or web interface.
Managing Notifications:
Option E is correct because GitHub Mobile allows users to manage notifications, keeping them up to date with their repositories, issues, pull requests, and other activities on GitHub.
Incorrect Options:
Option A is incorrect because GitHub Mobile cannot be used as a self-hosted runner.
Option B is incorrect because managing enterprise and organization settings is not supported in GitHub Mobile.
Option C is incorrect because GitHub Mobile does not offer a chat or voice calling feature.
Option D is incorrect because forking and cloning repositories are not actions available in GitHub Mobile.
In GitHub, why is it recommended to deploy from your feature branch before merging into the main branch?
It is recommended to deploy from your feature branch before merging into the main branch to ensure the changes are verified and validated in a production environment. This practice helps in identifying any potential issues or bugs in a real-world scenario before the changes are permanently integrated into the main branch. By deploying from the feature branch, developers can catch and address issues early, reducing the risk of introducing bugs into the main branch, which is usually considered the stable branch.
What is the purpose of GitHub Sponsors?
GitHub Sponsors is a program designed to provide a platform for developers and companies to financially support open-source projects and their maintainers.
Financial Support for Open Source Projects:
Option D is correct because the main purpose of GitHub Sponsors is to allow members of the developer community, including individuals and organizations, to financially support open-source projects and maintainers. This helps sustain open-source development by providing developers with the resources they need to continue their work.
Incorrect Options:
Option A is incorrect because GitHub Sponsors is not based on project popularity (e.g., stars); it is based on voluntary contributions.
Option B is incorrect because while GitHub provides the platform, the purpose of GitHub Sponsors is not for GitHub itself to fund projects, but to enable the broader community to do so.
Option C is incorrect because GitHub Sponsors is not a marketplace for purchasing software but a platform for supporting developers.
Which of the following are included as pre-defined repository roles?
(Each answer presents a complete solution. Choose three.)
GitHub provides several pre-defined repository roles that determine the level of access and permissions a user has within a repository. The roles that are included by default are:
Triage: Allows users to manage issues and pull requests without write access to the code.
Maintain: Provides more extensive access, including managing settings, but without full administrative control.
Write: Grants permission to push changes and manage issues and pull requests.
Roles like 'Security' and 'Delete' are not standard pre-defined roles, and 'View' is generally referred to as 'Read' in GitHub's permission structure.
Merri
4 days agoMaryann
19 days agoHershel
21 days agoMike
28 days agoHyman
1 months agoAlyce
2 months agoJoanne
2 months agoSheldon
2 months agoYaeko
2 months agoReuben
2 months agoRyann
3 months agoPauline
3 months agoWillow
3 months agoDesmond
3 months agoEnola
3 months agoJulie
4 months agoRobt
4 months agoEssie
4 months agoCarlee
4 months agoHuey
5 months agoChau
5 months agoGerri
5 months agoVivienne
5 months agoJoana
5 months agoElliott
6 months ago