Skip to content

Commit c96e525

Browse files
committed
docs: change ci link
1 parent af3354a commit c96e525

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

.github/workflows/issue-close-require.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ jobs:
1212
permissions:
1313
issues: write
1414
runs-on: ubuntu-latest
15-
if: github.repository == 'module-federation/universe'
15+
if: github.repository == 'module-federation/core'
1616
steps:
1717
- name: need reproduction
1818
uses: actions-cool/issues-helper@v3

.github/workflows/issue-labeled.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ on:
66

77
jobs:
88
reply-labeled:
9-
if: github.repository == 'module-federation/universe'
9+
if: github.repository == 'module-federation/core'
1010
runs-on: ubuntu-latest
1111
steps:
1212
- name: contribution welcome

apps/docs/README.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Before you begin, make sure you have the following installed on your machine:
1111
- nx
1212
- yarn
1313
14-
You also need a GitHub account and a fork of the https://github.com/module-federation/core[module-federation/universe] repository.
14+
You also need a GitHub account and a fork of the https://github.com/module-federation/core[module-federation/core] repository.
1515

1616
## Setting up your environment
1717

@@ -22,7 +22,7 @@ Documentation website consists of 2 applications:
2222
2323
To set up your environment, follow these steps:
2424

25-
1. Clone your fork of the module-federation/universe repository to your local machine.
25+
1. Clone your fork of the module-federation/core repository to your local machine.
2626
2. Navigate to the `apps/docs` folder inside the cloned repository.
2727
3. Run `npm install` to install the dependencies.
2828
4. By default, serving\building will pull the changes from the `main` branch. To use it, run `nx run docs:serve`. Along with it there's a `local` configuration, that provides an ability to rely on the files within the filesystem. Can be used by running `nx run docs:serve:local`
@@ -44,7 +44,7 @@ To make changes to the documentation, follow these steps:
4444
4545
## Submitting pull requests
4646

47-
Once you are happy with your changes, you can submit a pull request to the module-federation/universe repository. A pull request is a way of proposing your changes to be merged into the main branch of the repository.
47+
Once you are happy with your changes, you can submit a pull request to the module-federation/core repository. A pull request is a way of proposing your changes to be merged into the main branch of the repository.
4848

4949
To submit a pull request, follow these steps:
5050

@@ -54,7 +54,7 @@ To submit a pull request, follow these steps:
5454
4. Select your fork and branch as the source and the main branch as the destination.
5555
5. Fill in the title and description of your pull request and click on "Create pull request".
5656
57-
Your pull request will be reviewed by the maintainers of the `module-federation/universe` repository as well as by a technical writer who will check your content for accuracy, clarity, and adherence to Google Developers Documentation Style Guide. The technical writer may suggest some changes or improvements to your content before merging it to the main branch. and they will provide feedback or approve it.
57+
Your pull request will be reviewed by the maintainers of the `module-federation/core` repository as well as by a technical writer who will check your content for accuracy, clarity, and adherence to Google Developers Documentation Style Guide. The technical writer may suggest some changes or improvements to your content before merging it to the main branch. and they will provide feedback or approve it.
5858

5959
## Conclusion
6060

0 commit comments

Comments
 (0)