Question

1. What is rebase used for in the centralized workflow? 2. In the feature branch workflow, are feature branches checked in to GitHub (you can read any reference to BitBucket as GitHub here as well, these are written by Atlassian, which makes a GitHub-like system called BitBucket) . What branch is used as the basis of a feature branch in the GitFlow workflow? What branch or branches is a hotfix branch merged into in a GitFlow workflow? 4. How are pull requests used in the Forking workflow . (Opinion) Which workflow is best for small teams? Which workflow is best for open-source projects with distributed contributors? 6. How many different changes should be in a single commit? Why? 7. What kinds of information should be in a commit message? Should it include details of the actual code modifications?

Answer 1

1.

Bit Bucket was the product of Atlassian

Create commits using git add, git commit, and git push.
Pull from collaborators using git pull --rebase and git push.
Pull from parent using git pull origin <parent> and git push.

2.

The arrangement interior Atlassian's Bitbucket Server group is continuously to consolidate include branches, and require that branches are combined through a drag ask for quality and code audit. But the group isn't as well strict around fast-forward.
we talked about the Git Include Department Workflow. This workflow makes a difference organize and track branches that are centered on commerce space highlight sets. Other Git workflows just like the Git Forking Workflow and the Gitflow Workflow are repo centered and can use the Git Include Department Workflow to oversee their branching models. This record illustrated a high-level code illustration and anecdotal illustration for executing the Git Include Branch Workflow. A few key affiliations to form with the Highlight Department Workflow are: focused on branching patterns can be utilized by other repo arranged workflows promotes collaboration with group individuals through drag demands and combine audits

3.

one time recently I drag, I make beyond any doubt I am on the proper department. I have GIT Bash autocompletion introduced, this tells me the department within the incite. Something else, the taking after command is sweet to know to list out the branches I have locally as well assign which department I am right now on.

$ git branch

The checked out department will have a * some time recently the title. On the off chance that the return assigns anything other at that point ace at that point switch to ace

$ git checkout master

Once on ace and prepared to drag overhauls, I utilize the following

$ git pull origin master

The git drag command combines two other commands, git bring and git blend. When doing a bring the coming about commits are put away as inaccessible department permitting you to audit the changes some time recently consolidating. Blending on the other hand can include extra steps and banners within the command, but more on that afterward. For presently, I'll adhere with git drag

$ git checkout -b mynewfeaturebranch

This command will make a modern department from ace as well checkout out that modern department at the same time. Doing a git department will list out the branches in my neighborhood repo and put a * some time recently the department that's checked out.
  
master * mynewfeaturebranch

here's a command that that allows me to form a unused department from any other department whereas having checked out however another department

$ git checkout -b transactionfailmessage master

I am working on my modern highlight department, it may be a great thought to commit frequently. This permits me to move forward without fear that if something goes off-base, otherwise you got to back out for a few reason, I do not lose as well much work. Think of committing like that spare button propensity you have got so well programed into you. Each commit too tells a small bit around what I fair worked on. That's critical when other devs on the group are investigating my code. It's superior to have more commits with messages that clarify the step versus one expansive commit that gleams over vital subtle elements.

I am making changes in my extend, these are all unseated overhauls. With each commit there most likely will be augmentations, and there will moreover be cancellations from time to time.

$ git status

include records, I can include them independently or I can include all at once. From the root of the extend I can utilize
$ git add

In arrange to evacuate erased records from the form control, I can once more either evacuate independently or from the root address them all

$ git add -u
$ git add --all

All the going before commands will organize the overhauls for commitment. In case I run a git status at this point, I will see my overhauls displayed in an unexpected way, ordinarily beneath the heading of Changes to be committed:. At this point, the changes are as it were organized and not however committed to the department

$ git commit -m "a commit message"

4.

Within the Forking Workflow, a designer pushes a completed highlight to their own open store rather than a shared one. After that, they record a drag ask to let the venture maintainer know that it’s prepared for review. The notice perspective of drag demands is especially valuable in this workflow since the venture maintainer has no way of knowing when another designer has included commits to their Bitbucket store.
Since each designer has their claim open store, the drag request’s source store will contrast from its goal store. The source store is the developer’s open store and the source department is the one that contains the proposed changes. On the off chance that the designer is attempting to merge the include into the most codebase, at that point the goal store is the official venture and the goal department is master. Pull demands can too be utilized to collaborate with other designers exterior of the official extend. For case, on the off chance that a engineer was working on a include with a partner, they may record a drag ask using the teammate’s Bitbucket store for the goal rather than the official venture. They would at that point utilize the same include department for the source and goal branches.
how drag demands can be utilized within the Forking Workflow. It is similarly pertinent to designers working in little groups and to a third-party designer contributing to an open source project. In the example, Mary may be a engineer, and John is the extend maintainer. Both of them have their possess open Bitbucket stores, and John’s contains the official extend.
signing in to Bitbucket, navigating to repository, and clicking the Fork button.

ACTIONS:

Clone
Create branch
Create pull request
Compare
Fork

After filling out the name and description for the forked repository

git clone https://[email protected]/user/repo.git

Mary needs to create a new branch for the feature. This branch will use as the source branch of the pull request.

git checkout -b some-feature
# Edit code for your requirement
git commit -a -m "Add first draft of some feature"

5.

We've been utilizing the Github stream in groups of 2-10 individuals for some a long time presently. We work on include branches, combine after code review using the github web UI. Here's some things that offer assistance us: - Make a run the show that anything that's in ace can be conveyed by anybody at any time. This will uphold teach for code survey, but moreover for presenting changes that f.e. require movements. You'll utilize include banners more, part db pattern changes into a few organizations, make code work with both construction form, etc. All great hones that you'll require besides after you reach bigger scale and run into issues with diverse forms of code running concurrently amid deployments. - In case you're utilizing Github, check out the as of late included alternatives for controlling blending. Empower department assurance for ace, so that as it were drag ask that are green on CI and have been surveyed can be blended. Empower diverse dropdown alternatives for the consolidate button

On the off chance that your workflows are not as well complex, I recommend utilizing Metatask. This basic web-based workflow app permits you to robotize trade forms inside minutes. You can characterize a reusable format for any prepare as a list of errands with trustees and due dates. Assignments list is a straightforward concept for all colleagues so you'll start working on your forms together without hours of framework onboarding. Metatask contains a library of pre-made layouts you'll be able utilize as an case with most standard trade forms like e.g. representative onboarding, excursion ask or cost report.

You can track all running processes in one place

6.

The most straightforward way to turn numerous commits in a include department into a single commit is to reset the include department changes within the ace and commit everything once more.
Switch to the ace department and make beyond any doubt you're up to date.

git checkout master
git fetch
git pull
Merge the feature branch into the master branch

git merge feature_branch

git reset origin/master

Git now considers all changes as unstaged changes.
We can add these changes as one commit.
Adding will also add untracked files.
git add --all

git commit

Note that usually not touching the highlight department at all. In case you'd combine the highlight department into the ace once more at a afterward arrange all of its commits would return within the log. You may too do it the other way circular (blending ace into the branch and resetting to the master state) but this will annihilate your commits within the include department, meaning you'll not thrust it to root.

7.

Communication is seemingly the foremost critical of those. With the rise of dispersed groups it is greatly imperative to preserve great propensities of communication in all shapes. Given the contrasts in timezones, composed communication gets to be indeed more important. Commit messages are vital implies of communication between group individuals and for the lifecycle of the group: its past and its future.

To speed up the reviewing process.
To help us write a good release note.
Write the summary line and description of what you have done in the imperative mode, that is as if you were commanding someone. Start the line with "Fix", "Add", "Change" instead of "Fixed", "Added", "Changed"

Don't end the summary line with a period - it's a title and titles don't end with a period.

On the off chance that it appears troublesome to summarize what your commit does, it may be since it incorporates a few consistent changes or bug fixes, and are superior part up into a few commits utilizing git add -p.