git – Repositórios Que não são meus aparecem em ‘repositórios”

GitHub

Galera, sem bincadeira… eu já estou tentando corrigir esse erro a MESES, e não consigo!

Bom, o problema é o seguinte… na minha aba de Repositories, lá tem os meus repositórios… até ai tudo bem, mas Aparece uns repositórios aleatórios, no meu caso – barbosaadriano/shareflix-api-alurachallenge e microsoftvscode-arduino. Eu quero tirar eles dai!!!

Observações: Esses dois repositórios, eu apenas fiz um issue, e a praga não sai mais de repositories 😒 – Se alguém poder me ajudar, eu agradeço

inserir a descrição da imagem aqui

git – what would be the best approach to run multiple git commands (possibly hundreds)?

I have a script that runs many many maaaaaany separate git commands. Each one of those commands mean that a new process has to be created, all the environment has to be read from the FS (which in a slow computer like mine with a big project means that it can get reeeeally slow) and a looooooong etc.

Is there a way in which git (itself) can be started so that multiple commands can be run interactively against a single process…. say, something like:

( echo "status"; echo "add afile"; echo 'commit -m "blah"' ) | git terminal

How to specify which Chrome version (canary or regular) ‘start chrome’ opens (windows, git bash)

When I run start chrome www.google.com form a Git Bash terminal on Windows 10, Chrome Canary get openend. How can I specify that I want to open the regular version of Chrome?

git – Managing Documentation / Source Control for a Full-Stack Application Across Multiple Repos

TL;DR

I have a moderately sized/complexity web application (Angular 11) in one repo and a standalone REST API (.NET Core 3 / C#) in another repo, and am trying to figure out the most efficient way to include MkDocs / Read the Docs in the project.


We’ve been building a full-stack web application with multiple core components in two repos:

  1. Frontend
    • Angular 11 Web application (compiled / deployed as a standalone app and not served from .NET)
  2. Backend
    • .NET Core 3 / C# REST API
    • RabbitMQ brokers for handling certain asynchronous actions
    • Windows scheduled task / console app for a nightly job

This has worked reasonably well, but as we’re building out the documentation more and more we’re running into documentation consistency issues across the two repos. E.g. in describing certain elements of the front end it makes sense to discuss the data, as this is a very “data-centric” app. However then it seems redundant to discuss those concepts in the documentation for the backend repo.

I’ve read a lot about the “monorepo vs. multi-repo” debate, and this seems to be a matter of opinion with some folks for one and strongly opposed to the other, and vice versa. (Similar post here).

As I see it I have a few options:

  1. Maintain multiple repositories as I have it now, and deal with the documentation headaches

    • Default option right now, as it requires no additional effort at this point in time
  2. Merge everything into a monorepo, which makes documentation easier but

    • As the project grows and more developers / analysts join, this could potentially complicate things (or, so I would expect?)
  3. Create a separate repository solely for documentation

    • Introduces more complexity to the scheme of things and possibly adds another barrier to developers updating documentation

What are some recommendations based on what other teams are doing?

git – Update theme from github whenever there is a push

We have a proprietary theme that is hosted on a private git repo. There are a bunch of people working on the theme and we used a plugin called Github updater to update theme files on the server whenever we pushed to the master branch.

This worked flawlessly for a while. But the plugin is now discontinued by its creator. I’m looking for a preferably free replacement for this plugin. I’ve searched on the internet but couldn’t find a reliable solution that is not too difficult to use, please help!

git – Visual Studio Code not syncing with GitHub after merging branch

I merged a branch to the main branch in VSCode that’s synced with GitHub. The branch successfully merged without pushing uncommitted changes as expected but then I realized the branch needed to be deleted. So I committed those changes, merged the branch with main, then deleted it. Now GitHub has the correct files and stuff for the main branch but VSCode does not… what did I do?

PS I’m new to using GitHub

Basically, here’s one of my functions in VSCode:

def valid(play, current_card):
  if play(0) != current_card(0):
    if play(1) != current_card(1):
      return False
  else:
    return True

And this is what it should be (as it is in GitHub):

def valid(play, current_card):
  # if valid play
  if (play(0) in ("R", "G", "B", "Y")):
    if (len(play) == 2) and (play(0) == current_card(0) or play(2:) == current_card(2:)):
      # if regular card
      if (int(play(1)) < 9 and int(play(1)) > 0):
        return True
      elif play(1) == "X":
        return True
    elif len(play) == 3 and (play(1:2) in ("+2", "RV")):
      return True
  elif play == "W" or play == "W+4":
    return True
  return False

def find_card(card, hand):
  for i in range(len(hand)):
    if card in hand(i):
      return i

How can I fix this?

git – Simple Solution – error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)

I followed most of the answers but not solved my problem.

In my case, the answer is very simple

I encountered this error when pushing GIT through an ADSL Broadband Wi-Fi network with low signal strength, low stability, and low speed.

Then,
I was able to push it very successfully when I pushed it into the GIT through a Fibre Broadband Wi-Fi network with greater signal strength, greater stability, and higher speed.

Error:

enter image description here

github – how to remove a large file-from-git-history and how to push to remote git repositories

I just started working on a new project and as you would expect one of the first things I did was to download its git repository from GitHub. These were just some scripts and should have been very small ~5M, but the clone from GitHub took about one hour as the full repo folder was 1.5G… (with the biggest size under .git/objects/pack)

git – GitHub – Como aceitar PR automaticamente após revisões?

Estou realizando um projeto no GitHub e gostaria de estruturar algo que após uma quantidade determinada de aprovações na revisão, que ocorresse o merge do pull request de forma automática.

Sei que isso é possível, pois já ouvi falar desse processo em algumas ferramentas como o GitLab pago. Além disso, com o GitHub Actions algumas automações têm se tornado realidade.

Já tentei procurar em alguns links próprios do GitHub, mas o máximo que encontrei foi isso: https://docs.github.com/pt/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
, mas nada explicito quanto ao número de aprovações.

¿Para que sirve git revert HEAD~5..HEAD~3?

Hasta ahora se que se puede usar git revert con un solo commit; Ejemplo: git revert HEAD~1

Pero, ¿que pasa si pongo otro commit? Ejemplo: git revert (commit 1)..(commit 3)