Skip to content

Update Control Plane links #591

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 14, 2024
Merged

Update Control Plane links #591

merged 1 commit into from
May 14, 2024

Conversation

samueldemoura
Copy link
Contributor

@samueldemoura samueldemoura commented May 14, 2024

This change is Reviewable

Summary by CodeRabbit

  • Documentation

    • Updated URLs from controlplane.com to shakacode.controlplane.com for account setup and documentation links.
  • Style

    • Updated the "Control Plane" link in the header to point to shakacode.controlplane.com.

@samueldemoura samueldemoura self-assigned this May 14, 2024
Copy link

coderabbitai bot commented May 14, 2024

Walkthrough

The recent updates focus on changing URLs from controlplane.com to shakacode.controlplane.com across various documentation and web resources. This includes account setup links, quickstart guides, and site navigation elements. These changes ensure all references point to the new domain, enhancing consistency and user experience.

Changes

Files Change Summary
.controlplane/readme.md Updated URLs for account setup and documentation links to shakacode.controlplane.com.
README.md Modified the link for "Control Plane" to shakacode.controlplane.com.
app/views/pages/_header.html.erb Updated the link to "Control Plane" to shakacode.controlplane.com.

In the warren of code, URLs did change,
From controlplane to shakacode they rearrange.
With links anew, the path is clear,
For users to follow without any fear.
A hop, a skip, and a joyous cheer,
The rabbit's code now brings us near! 🐇


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between d76a845 and 4d0b389.
Files selected for processing (3)
  • .controlplane/readme.md (2 hunks)
  • README.md (1 hunks)
  • app/views/pages/_header.html.erb (1 hunks)
Files skipped from review due to trivial changes (1)
  • app/views/pages/_header.html.erb
Additional Context Used
LanguageTool (25)
.controlplane/readme.md (5)

Near line 33: Possible missing comma found.
Context: ...cpln login to ensure access. For more informatation check out the [docs here](https://shaka...


Near line 56: Loose punctuation mark.
Context: ...ontrolplanedirectory. 1./templates: defines the objects created with the c...


Near line 58: Loose punctuation mark.
Context: ...n applycommand. 2./controlplane.yml`: defines your application, including the...


Near line 59: Loose punctuation mark.
Context: ... location, and app name. 3. Dockerfile: defines the Docker image used to run th...


Near line 60: Loose punctuation mark.
Context: ...app on Control Plane. 4. entrypoint.sh: defines the entrypoint script used to r...

README.md (20)

Near line 14: Style-wise, it’s not ideal to insert an adverb (‘easily’) in the middle of an infinitive construction (‘to deploy’). Try moving the adverb to avoid split infinitives.
Context: ....md](./.controlplane/readme.md) for how to easily deploy this app to Control Plane. The instructions lev...


Near line 27: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ..., Written by Paul Benigeri, October 12, 2018](https://github.com/shakacode/react_on_...


Near line 33: Possible missing comma found.
Context: ...ebpack v5+ and Shakapacker for React on Rails including code splitting with loadable-...


Near line 80: Possible typo: you repeated a word
Context: ...line) + Javascript Development without Rails + Rails Integration + [Web...


Near line 99: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...om/smarter-css-builds-with-webpack/). - Example of enabling hot reloading of both JS an...


Near line 99: You might be missing the article “the” here.
Context: ...velopment mode. Change your code. Save. Browser updates without a refresh! - Example of...


Near line 102: The usual collocation for “independently” is “of”, not “from”. Did you mean “independently of”?
Context: .... - Enabling development of a JS client independently from Rails using the [Webpack Dev Server](ht...


Near line 104: ‘brand new’ seems to be a compound adjective before a noun. Use a hyphen: “brand-new”.
Context: ...an existing Rails app. You don't need a brand new single page app! - Example setting up R...


Near line 104: A punctuation mark might be missing here.
Context: ... app. You don't need a brand new single page app! - Example setting up Ruby and Java...


Near line 120: Possible typo: you repeated a word
Context: ... with plain HTML 1. Heroku for Rails 7 deployment 1. [Deployment to the ControlPlane](.controlplane/read...


Near line 131: The operating system from Apple is written “macOS”.
Context: ...which redis-server. If missing and on MacOS, install with Homebrew (`brew install r...


Near line 161: Unpaired symbol: ‘]’ seems to be missing
Context: ...pp your-app ``` ## Testing + See [Yak Shaving Failing Integration Tests wi...


Near line 165: Consider a shorter alternative to avoid wordiness.
Context: ...to run foreman start -f Procfile.spec in order to have webpack automatically recompile th...


Near line 165: Consider shortening this phrase to just ‘whether’, unless you mean ‘regardless of whether’.
Context: ...ec is configured to automatically check whether or not this process is running. If it is not, ...


Near line 184: After the expression ‘for example’ a comma is usually used.
Context: ...s a great way to learn about this! For example in [client/app/bundles/comments/compone...


Near line 203: A comma might be missing here.
Context: ...SASS The tutorial makes use of a custom font OpenSans-Light. We're doing this to sho...


Near line 210: Loose punctuation mark.
Context: ...> ``` 1. Procfile.dev: Starts the Webpack Dev Server and Rails...


Near line 211: Loose punctuation mark.
Context: ...Procfile.static: Starts the Rails server and generates s...


Near line 214: Possible typo: you repeated a word
Context: ...](https://github.com/justin808/), along with with many others. See [contributors.md](docs...


Near line 225: Insert a comma after thanking someone.
Context: ...bout/index.html#work-with-us). --- ## Thank you from Justin Gordon and [ShakaCode](http...

Additional comments not posted (3)
.controlplane/readme.md (2)

24-24: URL update for Control Plane account setup looks good.


34-34: URL update for Control Plane documentation looks good.

README.md (1)

10-10: URL update for Control Plane looks good.

@samueldemoura samueldemoura merged commit acfe281 into master May 14, 2024
3 checks passed
@samueldemoura samueldemoura deleted the chore/update-cpln-links branch May 14, 2024 21:51
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.

1 participant