Skip to content

Conversation

@danilolmc
Copy link
Contributor

No description provided.

@javascript-translate-bot

Error: the article already has PR number in the Progress Issue #1, it's 411 ⁉️

Copy link
Member

@nazarepiedady nazarepiedady left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just found two points to be reviewed, so I will pass to you @jonnathan-ls the responsibility of reviewing the rest.

@danilolmc
Copy link
Contributor Author

/done

@javascript-translate-bot javascript-translate-bot requested a review from a team January 9, 2024 14:42
Copy link
Contributor

@jonnathan-ls jonnathan-ls left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks Good To Me (LGTM)

@jonnathan-ls
Copy link
Contributor

jonnathan-ls commented Jan 13, 2024

I just found two points to be reviewed, so I will pass to you @jonnathan-ls the responsibility of reviewing the rest.

Adicionei minha aprovação!

Por mais que ainda tenha solicitado alterações @nazarepiedady, acabou marcando a opção de review como comentário ... mas considerando que o @danilolmc já adicionou as alterações, entendo que a solicitação foi atendida, configurando como aprovada, então seguirei com o merge deste PR.

Quando adicionar uma revisão que tenha solicitações de mudança @nazarepiedady, procure marcar a opção:

Request changes
Submit feedback that must be addressed before merging.

Assim, o github registra as considerações e o BOT configurado do repositório consegue atuar, acho que foi por isso que ele acabou não atualizando o status deste PR, já que registrou como comentário em vez de request changes.

image

Obs.: Marcar como request changes e approved, mantém o vinculo de detalhes da aprovação associadas ao PR 01

@jonnathan-ls jonnathan-ls merged commit d43daf7 into javascript-tutorial:master Jan 13, 2024
@javascript-translate-bot

Error: the article has another PR number in the Progress Issue #1, it's 411, not 413 ⁉️

@jonnathan-ls
Copy link
Contributor

jonnathan-ls commented Jan 13, 2024

Error: the article has another PR number in the Progress Issue 1, it's 411, not 413 ⁉️

Updated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants