Repository navigation
feat(notion): incluir contexto de reuniões na documentação - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumo
Contexto do histórico
A branch
test/n8n-docscontinha um commit anterior que já havia sido integrado àmainpor squash. Isso fazia um merge direto reapresentar conflitos em documentação, scripts e workflows, apesar demaine o estado pré-Notion terem conteúdo idêntico. Este PR parte diretamente demaine transporta somente a mudança do Notion, evitando reescrever a branch histórica.Validação
node scripts/build-versioned-workflows.mjs --checknode scripts/validate-repository.mjsjqgit diff --checkorigin/mainsem conflitosA execução real contra Notion e OpenAI continua dependente das credenciais locais.