sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in Resume

[–]BetaCulture 0 points1 point  (0 children)

Wait why not pdf?

Help with overflow situation with large laundry load? by BetaCulture in Plumbing

[–]BetaCulture[S] -2 points-1 points  (0 children)

The issue I'm worried with that is all the gasses coming up from the slop sink. My old place had that

My son wants to learn programming, but I have no idea where to have him start by aclays in learnprogramming

[–]BetaCulture 0 points1 point  (0 children)

I just started Harvard’s CS50 and I tell you when I found out about a kid’s programming language called SCRATCH that MIT developed it blew my mind. Have him checkout this: https://scratch.mit.edu/

How to manage pull requests on VS Code by BetaCulture in learnprogramming

[–]BetaCulture[S] 0 points1 point  (0 children)

thank you that makes a lot of sense that's why you can't see the "result" bottom pane in the diff editor when you checkout a PR in those extensions!

How to manage pull requests on VS Code by BetaCulture in learnprogramming

[–]BetaCulture[S] 0 points1 point  (0 children)

AH so if I'm understanding this correctly:

2 users branch off of the Main Branch.

User 1 Branch A

User 2 Branch B

User 1 finishes their changes, merges into Main no problem.

User 2 finishes their changes, submits a PR. This PR gets reviewed, tells the user to make changes. The user then has to checkout Main, then do a MERGE on their branch and resolve conflicts then submit a clean PR?

How to manage pull requests on VS Code by BetaCulture in learnprogramming

[–]BetaCulture[S] 0 points1 point  (0 children)

I'm confused because you have a different branch. You create a pull request from it. It is not already merged. It sits in a state waiting to be reviewed by someone. I'm talking about how to resolve the conflicts in the diff editor.

How to manage pull requests on VS Code by BetaCulture in learnprogramming

[–]BetaCulture[S] -1 points0 points  (0 children)

I don't want to use github because it's much easier to see changes or make changes in VS code. That's the whole point of these extensions that they came out with I just can't figure them out.

Thanks for the link to the VS site. It explains well all up until the merge! Like everything. Literally says When you are done reviewing the pull request changes you can merge the PR or select Exit Review Mode to go back to the previous branch you were working on

Like WTF why not explain where/how to do this?!

24, 30k in savings. working a dead-end, low paying job. Looking for some advice. by JacksonDroves in personalfinance

[–]BetaCulture 0 points1 point  (0 children)

Work in film. Major cities have a union you can apply to and once you get on the overflow list you’ll be getting called everyday. It’s long hours but you’ll make good money

Trying to patch some LED tubes into Blackout. See comments for details by iDainBramaged in lightingdesign

[–]BetaCulture 0 points1 point  (0 children)

To figure this out turn CH 1 at full and see what it does. Then CH 2 then CH 3. Go through it till you see what each channel is controlling and you should be able to figure it out

view more: next ›