Correct capitalization of GitHub in README#62
Merged
fivetran-avinash merged 2 commits intoMagicBot/consolidate-source-packagefrom Aug 14, 2025
Merged
Correct capitalization of GitHub in README#62fivetran-avinash merged 2 commits intoMagicBot/consolidate-source-packagefrom
fivetran-avinash merged 2 commits intoMagicBot/consolidate-source-packagefrom
Conversation
"GitHub" should be camelcase. The live version of the README inconsistently capitalizes it. This PR correct that issue.
fivetran-catfritz
approved these changes
Apr 29, 2025
f8ead84
into
MagicBot/consolidate-source-package
3 of 9 checks passed
fivetran-avinash
added a commit
that referenced
this pull request
Aug 14, 2025
* Consolidate dbt source into transform * Q2 FY26 Automatic Package Updates (#65) * Q2 FY26: Apply automated update. * Q2 FY26: Update auto-release workflow only. --------- Co-authored-by: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com> * packages, dbt_project, changelog, readme * Generate dbt docs via GitHub Actions * Correct capitalization of GitHub (#62) "GitHub" should be camelcase. The live version of the README inconsistently capitalizes it. This PR correct that issue. Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com> * Changelog * Generate dbt docs via GitHub Actions --------- Co-authored-by: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com> Co-authored-by: Avinash Kunnath <avinash.kunnath@fivetran.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: AK Krajewska <ak.krajewska@fivetran.com>
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.
"GitHub" should be camelcase. The live version of the README inconsistently capitalizes it. This PR correct that issue.
Please provide your name and company
Link the issue/feature request which this PR is meant to address
Detail what changes this PR introduces and how this addresses the issue/feature request linked above.
How did you validate the changes introduced within this PR?
Which warehouse did you use to develop these changes?
Did you update the CHANGELOG?
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?
If you had to summarize this PR in an emoji, which would it be?
💃
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.
PR Template
Community Pull Request Template (default)
Maintainer Pull Request Template (to be used by maintainers)