 we added the ability for anyone to suggest any missing command from the command palette. When collecting the feedback, we noticed that most of the missing commands were URLs to GitHub repos. 

Today, consider it solved, we now allow you to paste a GitHub URL into the command palette, hit enter, and we will deploy it.

If you already own the repo, we will simply deploy it to a new service. If it is a public repo that you do not own, we will create a new repo in your GitHub account and deploy that.

This is one of many improvements coming to the Command Palette. If you have any suggestions for a command or think something should be there that isn’t, just type it in the palette and press Shift + Enter. These alerts go straight to our company Discord where the team discusses them almost immediately.

When deploying a template, Railway keeps track of the upstream URL so we can check for updates. This was previously hidden in the UI. Now you can see the linked upstream repo in the service settings. We have now made it more obvious to disconnect the link or check for updates.

You can now disable GitHub triggers for a service on a per environment basis. If the trigger is disabled we will not automatically deploy when the repo is pushed. This is useful if you want to disable automatic deploys to the development environment and instead deploy with 

We will show a small message above the logs when the deploy fails to start because of a missing start command

Fixed a bug where you couldn’t transfer a project to a team with services

Fixed a bug where some logs would not appear in the correct order

Improved metro UI for users with VIEWER permission

https://res.cloudinary.com/railway/image/upload/v1648256408/docs/Command-OG_rggw1w.png

GitHub URL Deploys, Upstream URLs, Disable GitHub Triggers

Changelog #0074