dnrops
/
tuist
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Migrate tuist.io/docs -> docs.tuist.io (#3098)

This commit is contained in:
Iain Smith 2021-06-24 07:31:23 +01:00 committed by GitHub
parent bf9ad260fe
commit 209098bf07
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@ -5,5 +5,5 @@ that your contributions are licensed under the MIT License.
---
Before submitting the pull request, please make sure you have [tested your
changes](https://tuist.io/docs/contribution/testing-strategy/)
and that they follow the Tuist project [Manifesto](https://tuist.io/docs/contribution/manifesto/).
changes](https://docs.tuist.io/contributors/testing-strategy/)
and that they follow the Tuist project [Manifesto](https://docs.tuist.io/contributors/manifesto/).

2
projects/tuist/fixtures/app_with_tasks/Tuist/ProjectDescriptionHelpers/Project+Templates.swift
View File

@ -3,7 +3,7 @@ import ProjectDescription
/// Project helpers are functions that simplify the way you define your project.
/// Share code to create targets, settings, dependencies,
/// Create your own conventions, e.g: a func that makes sure all shared targets are "static frameworks"
/// See https://tuist.io/docs/usage/helpers/
/// See https://docs.tuist.io/guides/helpers/
extension Project {
/// Helper function to create the Project for this ExampleApp

2
projects/website/markdown/posts/2020-01-31-version-1.2.0/post.mdx
View File

@ -14,7 +14,7 @@ Firstly, warm welcome to another first-time Tuist contributor [Maciej Piotrowski
## Future of Tuist
There are plenty of ideas floating around what other features Tuist should have and [Pedro](https://github.com/pepibumur) laid them out in nicely in [The journey towards Tuist 2.0](https://github.com/tuist/tuist/issues/951). In addition, he also opened a work-in-progress PR for Tuist's [manifesto](https://github.com/tuist/tuist/pull/952). With more and more people joining the project it's very important to lay down the core principles in writing to ensure that everyone is up to speed. For more practical information we also have a new [Best Practices](https://tuist.io/docs/usage/best-practices/) section on the website. It is quite short at the moment, but will contain a growing list of things that can be useful for both new Tuist users and developers trying to improve their setup.
There are plenty of ideas floating around what other features Tuist should have and [Pedro](https://github.com/pepibumur) laid them out in nicely in [The journey towards Tuist 2.0](https://github.com/tuist/tuist/issues/951). In addition, he also opened a work-in-progress PR for Tuist's [manifesto](https://github.com/tuist/tuist/pull/952). With more and more people joining the project it's very important to lay down the core principles in writing to ensure that everyone is up to speed. For more practical information we also have a new [Best Practices](https://docs.tuist.io/building-at-scale/best-practices/) section on the website. It is quite short at the moment, but will contain a growing list of things that can be useful for both new Tuist users and developers trying to improve their setup.
## Focus on improving performance

2
script/install
View File

@ -83,4 +83,4 @@ rm -rf /tmp/tuistenv
rm /tmp/tuistenv.zip
ohai "tuistenv installed. Try running 'tuist'"
ohai "Check out the documentation at https://tuist.io/docs"
ohai "Check out the documentation at https://docs.tuist.io/"