teamoneline:


bro thanks for this video.. please from 4:59 of the video after the teacher typed "git merge update-readme --no-f" and hit enter..it takes him to another screen .. now the problem is i dont know what he pressed to return back to the normal bash interface after writing his commit message.
please what did key did he press??

chunis:


I didn't see the video but you are using the default git editor (VIM) to write merge commit messages. After writing the merge commit message (note that the greyed out letters at the end mean it wouldn't be included), follow the following steps:

1. Press ESC
2. Press :wq
3. Hit enter

When less busy maybe you should configure your own editor as the default editor in git

teamoneline:


thanks

teamoneline:


bro thanks for this video.. please from 4:59 of the video after the teacher typed "git merge update-readme --no-f" and hit enter..it takes him to another screen .. now the problem is i dont know what he pressed to return back to the normal bash interface after writing his commit message.
please what did key did he press??

samnelly4u:
guys please i need your help on this

function digitize(n) {


let str = String(n);
return str.split('').map(Number).sort();

}



Test Results:
Test Passed: Value == true
Test Passed: Value == true
Test Passed: Value == true
Expected: true, instead got: false
Expected: true, instead got: false

samnelly4u:
guys please i need your help on this

function digitize(n) {


let str = String(n);
return str.split('').map(Number).sort();

}



Test Results:
Test Passed: Value == true
Test Passed: Value == true
Test Passed: Value == true
Expected: true, instead got: false
Expected: true, instead got: false

sheygz:
Guys please which is a better practice and what could be the effect?
i)merging each feature branch to the develop branch locally and then pushing the develop branch remotely
ii)pushing each feature branch to the remote repo, doing a pull request and merging it to the remote develop branch

cc IsArray Don Pikko Guente

sheygz:
Guys please which is a better practice and what could be the effect?
i)merging each feature branch to the develop branch locally and then pushing the develop branch remotely
ii)pushing each feature branch to the remote repo, doing a pull request and merging it to the remote develop branch

cc IsArray Don Pikko Guente

DonPikko:
you are obviously doing the wrong thing then, what is the task

samnelly4u:


here is the task:
Given a non-negative integer, return an array or a list of the individual digits in order.

separate multiple digit numbers into an array

Parameters
n: Number - Number to be converted

Return Value
Array<Number> - Array of separated single digit integers

Examples
n Return Value
123 [1,2,3]
8675309 [8,6,7,5,3,0,9]

minions:
So, I have been trying to get a hang of this git workflow thingy. And this is my understanding.
1. You create a repo on github.
2.You clone using git clone url
3. From this clone which is the local repository we create a develop branch using git checkout -b develop
4.On the develop branch, we create a branch for each feature git checkout -b feature_branch
# we work from this feature branch.
5. When the specific feature is done, you switch to develop branch - git checkout develop.
6. You merge feature branch - git merge feature_branch
You repeat 1 to 6 for each feature. When done:

7. You switch to the clone repo on your pc which I will call master - git checkout master
8 You merge develop branch - git merge develop

9. You delete the feature branches git branch -d feature_branch.
10. Push to remote master on Hub.

Please, what comprises a feature would one call a login page a feature or a route that does a specific thing eg form Posting?

Question 2. Is there a way to get back to the correct workflow after messing up.
Question 3. Does it mean we don't push to master or merge to master clone on PC until all work is done ie until 4thweek?

Please someone that understands and has the time should please help out and correct my steps above. Ejoor. Bikonu.

samnelly4u:


here is the task:
Given a non-negative integer, return an array or a list of the individual digits in order.

separate multiple digit numbers into an array

Parameters
n: Number - Number to be converted

Return Value
Array<Number> - Array of separated single digit integers

Examples
n Return Value
123 [1,2,3]
8675309 [8,6,7,5,3,0,9]

teamoneline:


sincerely i couldn't just understand the whole git hub workflow . but this is what i did

-i created a repo on github with readme
-git clone <url>
-cd <url-folder>
-git checkout -b develop
-git checkout -b feature-bla-bla-bla
------then when i was done with that feature..:
- git add . (on that feature branch)
-git commit -m "bla bla bla"
-git push origin <branch name im pushing up to gitbub(feature-bla-bla-bla)>
-click on the green compare & pull request button on github and created a pull request, went to pivotaltracker and added pull request option(after integrating pivottr with github) then went on github and merged..
-came back to my local repo switch to develop branch from previous feature branch that was pushed and -- git pull origin master(on develop branch)
-git checkout -b another-feature-bla-bla-bla
-repeat till all features were done

----- when i was done i merged all the feature branches to develop branch on local repo.
and i stopped there. i did not even touch the master branch..
i dont know if am correct at all. i just did as the spirit leads. maybe when we get to camp it will be explained better. i just hope it wont be a criteria to kick one out..

minions:
So, I have been trying to get a hang of this git workflow thingy. And this is my understanding.
1. You create a repo on github.
2.You clone using git clone url
3. From this clone which is the local repository we create a develop branch using git checkout -b develop
4.On the develop branch, we create a branch for each feature git checkout -b feature_branch
# we work from this feature branch.
5. When the specific feature is done, you switch to develop branch - git checkout develop.
6. You merge feature branch - git merge feature_branch
You repeat 1 to 6 for each feature. When done:

7. You switch to the clone repo on your pc which I will call master - git checkout master
8 You merge develop branch - git merge develop

9. You delete the feature branches git branch -d feature_branch.
10. Push to remote master on Hub.

Please, what comprises a feature would one call a login page a feature or a route that does a specific thing eg form Posting?

Question 2. Is there a way to get back to the correct workflow after messing up.
Question 3. Does it mean we don't push to master or merge to master clone on PC until all work is done ie until 4thweek?

Please someone that understands and has the time should please help out and correct my steps above. Ejoor. Bikonu.

IlorinBoy1:
@minions, I want to agree with the flow below in response to your earlier post.
I heard we're never to touch the master branch. (Disclaimer: I'm as ignorant as you oo, also participating in the Bootcamp, everything I say here is my opinion).

Also, notice that the submission is by GitHub link, if you merge everything locally, i'm not sure GitHub will show ur merge history well, to enable you get scored by the bootcamp people (i'm not sure, cos i ddnt try).

Lastly, it's never too late to turn and follow the right way, once you know the right way - Dr Oby Ezekwesili.

gentletalkaktiv:
@teamoneline @minions

1. Create the repository on github and Clone the repository from github to your local machine.
2. Change the default head on github to develop from master(you can do that under settings manually), then checkout to develop locally and checkout again to the first feature branch.
3. git add, commit and push to this first feature branch remotely.
4. Raise a Pull Request and then merge with remote develop so develop is up to date.
5. Locally, checkout to develop then pull the remote develop branch into the local develop before you checkout and create another feature branch B then add, commit and push like above then raise a PR and merge with develop.
6. Continue the cycle like that of going back to develop after merging and pulling to create another feature branch.

N.B: Master branch is not meant to be worked on in this type of workflow, instead, develop becomes your default head (serves as master branch) in this case. Usually, only production ready code is merged into master and that will usually be done by the team lead on a real-world project.

Secondly, see each feature branch as a testing ground for something new you want to incorporate into your project such that you only merge it with develop when you are satisfied with all the features you intend to implement on the branch. This is so that develop holds the current working state of your project always.

This workflow also makes collaboration possible because you will do that a lot going forward as a fellow.
I hope this makes sense? Goodluck guys.

teamoneline:


that means we are not to touch any master branch both locally and remotely(github)? ...
please clarify your no 3. again.. did you mean the following

- git add .
-git commit -m "message"
-git push origin <feature branch> (that origin will now refer to the develop branch that was set as default on github ?)

teamoneline:


that means we are not to touch any master branch both locally and remotely(github)? ...
please clarify your no 3. again.. did you mean the following

- git add .
-git commit -m "message"
-git push origin <feature branch> (that origin will now refer to the develop branch that was set as default on github ?)

fxdrizzle:
Could anyone please refer me to a good tutorial on using the fetch api?

2O17:
https://davidwalsh.name/fetch

naijanoni:
Hello guys.
Just for encouragement:
I only started learning programming around May this year, and I just made it into the fellowship.
So if you just started programming, you too can get in soon, but u have to give it your all.
Right from May till now, it has been non-stop, no-sleep learning.
Three weeks before the bootcamp project, I had zero knowledge of anything backend. Node/express/database, I didn't know any of them. At the start of the bootcamp project, I didn't know how to use git. How I was able to cover so much in very little time still surprises me.
Get good resources and keep studying hard!. Your hard work would pay off soon.
Special thanks to my ogas Don Pikko, guente02, isarray for assisting whenever I ask questions here.
The journey begins, there is still a lot to learn.

naijanoni:
Hello guys.
Just for encouragement:
I only started learning programming around May this year, and I just made it into the fellowship.
So if you just started programming, you too can get in soon, but u have to give it your all.
Right from May till now, it has been non-stop, no-sleep learning.
Three weeks before the bootcamp project, I had zero knowledge of anything backend. Node/express/database, I didn't know any of them. At the start of the bootcamp project, I didn't know how to use git. How I was able to cover so much in very little time still surprises me.
Get good resources and keep studying hard!. Your hard work would pay off soon.
Special thanks to my ogas Don Pikko, guente02, isarray for assisting whenever I ask questions here.
The journey begins, there is still a lot to learn.

fxdrizzle:
Could anyone please refer me to a good tutorial on using the fetch api?

cc guente02 isArray Donpikko

guente02:
https://css-tricks.com/using-fetch/

fxdrizzle:
Could anyone please refer me to a good tutorial on using the fetch api?

cc guente02 isArray Donpikko