Skip to content

Commit

Permalink
add link to registryci docs (#567)
Browse files Browse the repository at this point in the history
  • Loading branch information
@ericphanson
ericphanson committed Jun 26, 2024
1 parent ddce19a commit c93ebce
Show file tree
Hide file tree
Showing 17 changed files with 17 additions and 17 deletions.
2 changes: 1 addition & 1 deletion src/AutoMerge/guidelines.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ function compat_violation_message(bad_dependencies)
# ...
```
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.
</details>
"""
Expand Down
2 changes: 1 addition & 1 deletion ...pe_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...pe_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Please make sure that you have read the [package naming guidelines](https://juli
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...pe_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...pe_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...ype_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down
2 changes: 1 addition & 1 deletion ...type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Hello, I am an automated registration bot. I help manage the registration proces
# ...
```

Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds.
Every package listed in `[deps]`, along with `julia` itself, must also be listed under `[compat]` (if you don't have a `[compat]` section, make one!). See the [Pkg docs](https://pkgdocs.julialang.org/v1/compatibility/) for the syntax for compatibility bounds, and [this documentation](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Upper-bounded-%5Bcompat%5D-entries) for more on the kinds of compat bounds required for AutoMerge.

</details>

Expand Down

2 comments on commit c93ebce

@ericphanson
Copy link
Member Author

Choose a reason for hiding this comment

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

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/109862

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v10.5.0 -m "<description of version>" c93ebce2e4691934acbe7969000576348c0952e9
git push origin v10.5.0

Please sign in to comment.