diff --git a/Project.toml b/Project.toml index 97c72ddb..2f0ae336 100644 --- a/Project.toml +++ b/Project.toml @@ -1,7 +1,7 @@ name = "RegistryCI" uuid = "0c95cc5f-2f7e-43fe-82dd-79dbcba86b32" authors = ["Dilum Aluthge ", "Fredrik Ekre ", "contributors"] -version = "10.0.1" +version = "10.1.0" [deps] Base64 = "2a0f44e3-6c83-55bd-87e4-b1978d98bd5f" @@ -34,6 +34,7 @@ LicenseCheck = "0.2" Pkg = "1" Printf = "<0.0.1, 1" Random = "<0.0.1, 1" +ReferenceTests = "0.9, 0.10" RegistryTools = "2.2" SHA = "<0.0.1, 0.7, 1" SimpleMock = "1" @@ -52,8 +53,9 @@ JSON = "682c06a0-de6a-54ab-a142-c8b1cf79cde6" Pkg = "44cfe95a-1eb2-52ea-b672-e2afdf69b78f" Printf = "de0858da-6303-5e67-8744-51eddeeeb8d7" SimpleMock = "a896ed2c-15a5-4479-b61d-a0e88e2a1d25" +ReferenceTests = "324d217c-45ce-50fc-942e-d289b448e8cf" Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40" TimeZones = "f269a46b-ccf7-5d73-abea-4c690281aa53" [targets] -test = ["Dates", "GitHub", "JSON", "Pkg", "Printf", "SimpleMock", "Test", "TimeZones"] +test = ["Dates", "GitHub", "JSON", "Pkg", "Printf", "SimpleMock", "ReferenceTests", "Test", "TimeZones"] diff --git a/docs/src/private-registries.md b/docs/src/private-registries.md index 59eddc66..ae8d17d6 100644 --- a/docs/src/private-registries.md +++ b/docs/src/private-registries.md @@ -13,9 +13,9 @@ After you have the registry configured, you can setup CI using RegistryCI by fol You will first need to copy the `.ci` folder in the root of the General registry to the root of your own registry. This folder contains some resources required for the RegistryCI package to work and update itself. If you do not need AutoMerge support, there is no need to copy the `stopwatch.jl` file in the `.ci` folder. -Next, you will need to copy the `ci.yml` and `update_manifest.yml` workflow files. +Next, you will need to copy the `registry-consistency-ci.yml` and `update_manifest.yml` workflow files. -The `ci.yml` file should be modified as follows if you have packages in your registry that depend on packages in the General registry. +The `registry-consistency-ci.yml` file should be modified as follows if you have packages in your registry that depend on packages in the General registry. If the packages in your registry depend on packages in other registries, they should also be added to `registry_deps` ```diff - run: julia --project=.ci/ --color=yes -e 'import RegistryCI; RegistryCI.test()' @@ -98,7 +98,7 @@ In that case you will also have to add the following - run: chmod 400 .ci/Manifest.toml + - run: chmod +x .ci/instantiate.sh ``` -in `ci.yml` and also `TagBotTriggers.yml` and `automerge.yml` (in which the above appears twice) files if those features are used. +in `registry-consistency-ci.yml` and also `TagBotTriggers.yml` and `automerge.yml` (in which the above appears twice) files if those features are used. ## Author approval workflow support diff --git a/src/AutoMerge/guidelines.jl b/src/AutoMerge/guidelines.jl index 7e823e12..7d709b25 100644 --- a/src/AutoMerge/guidelines.jl +++ b/src/AutoMerge/guidelines.jl @@ -244,7 +244,7 @@ function meets_name_ascii(pkg) end const guideline_julia_name_check = Guideline(; - info="Name does not include \"julia\" or start with \"Ju\".", + info="Name does not include \"julia\", start with \"Ju\", or end with \"jl\".", check=data -> meets_julia_name_check(data.pkg), ) @@ -254,6 +254,8 @@ function meets_julia_name_check(pkg) "Lowercase package name $(lowercase(pkg)) contains the string \"julia\"." elseif startswith(pkg, "Ju") return false, "Package name starts with \"Ju\"." + elseif endswith(lowercase(pkg), "jl") + return false, "Lowercase package name $(lowercase(pkg)) ends with \"jl\"." else return true, "" end @@ -264,6 +266,35 @@ function sqrt_normalized_vd(name1, name2) return VisualStringDistances.visual_distance(name1, name2; normalize=x -> 5 + sqrt(x)) end +# This check cannot be overridden, since it's important for registry integrity +const guideline_name_match_check = Guideline(; + info = "Name does not match the name of any existing package names (up-to-case)", + docs = "Packages must not match the name of existing package up-to-case, since on case-insensitive filesystems, this will break the registry.", + check=data -> meets_name_match_check(data.pkg, data.registry_master)) + +function meets_name_match_check(pkg_name::AbstractString, registry_master::AbstractString) + other_packages = get_all_non_jll_package_names(registry_master) + return meets_name_match_check(pkg_name, other_packages) +end + +function meets_name_match_check( + pkg_name::AbstractString, + other_packages::Vector; +) + for other_pkg in other_packages + if pkg_name == other_pkg + # We short-circuit in this case; more information doesn't help. + return (false, "Package name already exists in the registry.") + elseif lowercase(pkg_name) == lowercase(other_pkg) + return (false, "Package name matches existing package name $(other_pkg) up-to-case.") + end + end + return (true, "") +end + + +# This check looks for similar (but not exactly matching) names. It can be +# overridden by a label. const guideline_distance_check = Guideline(; info="Name is not too similar to existing package names", docs=""" @@ -302,18 +333,9 @@ function meets_distance_check( ) problem_messages = Tuple{String,Tuple{Float64,Float64,Float64}}[] for other_pkg in other_packages - if pkg_name == other_pkg - # We short-circuit in this case; more information doesn't help. - return (false, "Package name already exists in the registry.") - elseif lowercase(pkg_name) == lowercase(other_pkg) - # We'll sort this first - push!( - problem_messages, - ( - "Package name matches existing package name $(other_pkg) up to case.", - (0, 0, 0), - ), - ) + if lowercase(pkg_name) == lowercase(other_pkg) + # We handle this case in `meets_name_match_check` + continue else msg = "" @@ -492,7 +514,7 @@ function _valid_change(old_version::VersionNumber, new_version::VersionNumber) end const PACKAGE_AUTHOR_APPROVAL_INSTRUCTIONS = string( - "**If this was not a mistake and you wish to merge this PR anyway,", + "**If this was not a mistake and you wish to merge this PR anyway, ", "write a comment that says `[merge approved]`.**") const guideline_sequential_version_number = Guideline(; @@ -987,6 +1009,11 @@ function _run_pkg_commands( pushfirst!(cmd.exec, xvfb) end @info(before_message) + @info(string( + "IMPORTANT: If you see any messages of the form \"Error: Some registries failed to update\"", + "or \"registry dirty\", ", + "please disregard those messages. Those messages are normal and do not indicate an error.", + )) cmd_ran_successfully = success(pipeline(cmd; stdout=stdout, stderr=stderr)) cd(original_directory) @@ -1042,6 +1069,8 @@ function get_automerge_guidelines( (guideline_version_can_be_imported, true), (:update_status, true), (guideline_dependency_confusion, true), + # this is the non-optional part of name checking + (guideline_name_match_check, true), # We always run the `guideline_distance_check` # check last, because if the check fails, it # prints the list of similar package names in diff --git a/src/AutoMerge/util.jl b/src/AutoMerge/util.jl index 97cdf9b1..9286843a 100644 --- a/src/AutoMerge/util.jl +++ b/src/AutoMerge/util.jl @@ -84,44 +84,70 @@ function parse_registry_pkg_info(registry_path, pkg, version=nothing) return (; uuid=uuid, repo=repo, subdir=subdir, tree_hash=tree_hash) end -function _comment_disclaimer(; point_to_slack::Bool=false) - result = string( - "\n\n", - "Note that the guidelines are only required for the pull request ", - "to be merged automatically. However, it is **strongly recommended** ", - "to follow them, since otherwise the pull request needs to be ", - "manually reviewed and merged by a human.", - "\n\n", - "After you have fixed the AutoMerge issues, simply retrigger Registrator, ", - "which will automatically update this pull request. ", - "You do not need to change the version number in your `Project.toml` file ", - "(unless of course the AutoMerge issue is that you skipped a version number, ", - "in which case you should change the version number).", +##### +##### AutoMerge comment +##### + +# The AutoMerge comment is divided into numbered sections. +# Besides the "AutoMerge Guidelines which are not met" and "AutoMerge Guidelines have all passed!" +# sections, we keep these minimally customized, and instead simply include or exclude +# whole sections depending on the context. This way, users can understand the message +# without necessarily reading the details of each section each time. +# We hope they will at least read the section titles, and if they aren't +# familiar, hopefully they will also read the sections themselves. + +function _comment_bot_intro(n) + return string("## $n. Introduction\n\n", "Hello, I am an automated registration bot.", + " I help manage the registration process by checking your registration against a set of ","[AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). ", + "Meeting these guidelines is only required for the pull request to be **merged automatically**. ", + "However, it is **strongly recommended** to follow them, since otherwise ", + "the pull request needs to be manually reviewed and merged by a human.\n\n") +end + +function _new_package_section(n) + return string("## $n. New package registration", "\n\n", + "Since you are registering a new package, please make sure that you have read the ", + "[package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1).\n\n") +end + +function _what_next_if_fail(n; point_to_slack=false) + msg = """ + ## $n. What to do next + + 1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`)""" + if point_to_slack + msg = string(msg, " or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so!") + end + msg = string(msg, "\n", + "2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).", "\n\n", - "If you do not want to fix the AutoMerge issues, please post a comment ", - "explaining why you would like this pull request to be manually merged.", - ) + "If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged.") + if point_to_slack - result *= string( - " ", - "Then, send a message to the `#pkg-registration` channel in the ", - "[Julia Slack](https://julialang.org/slack/) to ask for help. ", - "Include a link to this pull request.", - ) + msg = string(msg, " Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help.") end - return result + msg = string(msg, "\n\n") + return msg +end + +function _automerge_guidelines_failed_section_title(n) + return "## $n. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met\n\n" end -function _comment_noblock() +function _automerge_guidelines_passed_section_title(n) + "## $n. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met!\n\n" +end + +function _comment_noblock(n) result = string( - "\n\n---\n", + "## $n. To pause or stop registration\n\n", "If you want to prevent this pull request from ", "being auto-merged, simply leave a comment. ", "If you want to post a comment without blocking ", "auto-merging, you must include the text ", "`[noblock]` in your comment. ", "You can edit blocking comments, adding `[noblock]` ", - "to them in order to unblock auto-merging.", + "to them in order to unblock auto-merging.\n\n", ) return result end @@ -129,13 +155,17 @@ end function comment_text_pass( ::NewVersion, suggest_onepointzero::Bool, version::VersionNumber, is_jll::Bool ) + # Need to know this ahead of time to get the section numbers right + suggest_onepointzero &= version < v"1.0.0" result = string( - "Your `new version` pull request met all of the ", + _comment_bot_intro(1), + _automerge_guidelines_passed_section_title(2), + "Your new version registration met all of the ", "guidelines for auto-merging and is scheduled to ", - "be merged in the next round.", - _comment_noblock(), - _onepointzero_suggestion(suggest_onepointzero, version), - "\n", + "be merged in the next round.\n\n", + _onepointzero_suggestion(3, suggest_onepointzero, version), + _comment_noblock(suggest_onepointzero ? 4 : 3), + "", ) return result end @@ -143,42 +173,34 @@ end function comment_text_pass( ::NewPackage, suggest_onepointzero::Bool, version::VersionNumber, is_jll::Bool ) + suggest_onepointzero &= version < v"1.0.0" if is_jll result = string( - "Your `new _jll package` pull request met all of the ", + _comment_bot_intro(1), + _automerge_guidelines_passed_section_title(2), + "Your new `_jll` package registration met all of the ", "guidelines for auto-merging and is scheduled to ", - "be merged in the next round.", - "\n\n", - _comment_noblock(), - _onepointzero_suggestion(suggest_onepointzero, version), - "\n", + "be merged in the next round.\n\n", + _onepointzero_suggestion(3, suggest_onepointzero, version), + _comment_noblock(suggest_onepointzero ? 4 : 3), + "", ) else result = string( - "Your `new package` pull request met all of the ", + _comment_bot_intro(1), + _new_package_section(2), + _automerge_guidelines_passed_section_title(3), + "Your new package registration met all of the ", "guidelines for auto-merging and is scheduled to ", - "be merged when the mandatory waiting period (3 days) has elapsed.", - "\n\n", - "Since you are registering a new package, ", - "please make sure that you have read the ", - "package naming guidelines: ", - "https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines", - "\n\n", - _comment_noblock(), - _onepointzero_suggestion(suggest_onepointzero, version), - "\n", + "be merged when the mandatory waiting period (3 days) has elapsed.\n\n", + _onepointzero_suggestion(4, suggest_onepointzero, version), + _comment_noblock(suggest_onepointzero ? 5 : 4), + "", ) end return result end -const _please_read_these_documents = string( - "Please make sure that you have read the ", - "[General registry README](https://github.com/JuliaRegistries/General/blob/master/README.md) ", - "and the ", - "[AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). ", -) - function comment_text_fail( ::NewPackage, reasons::Vector{String}, @@ -186,23 +208,17 @@ function comment_text_fail( version::VersionNumber; point_to_slack::Bool=false, ) - reasons_formatted = join(string.("- ", reasons), "\n") + suggest_onepointzero &= version < v"1.0.0" + reasons_formatted = string(join(string.("- ", reasons), "\n"), "\n\n") result = string( - "Your `new package` pull request does not meet ", - "the guidelines for auto-merging. ", - _please_read_these_documents, - "The following guidelines were not met:\n\n", + _comment_bot_intro(1), + _new_package_section(2), + _automerge_guidelines_failed_section_title(3), reasons_formatted, - _comment_disclaimer(; point_to_slack=point_to_slack), - "\n\n", - "Since you are registering a new package, ", - "please make sure that you have also read the ", - "package naming guidelines: ", - "https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines", - "\n\n", - _comment_noblock(), - _onepointzero_suggestion(suggest_onepointzero, version), - "\n", + _what_next_if_fail(4; point_to_slack=point_to_slack), + _onepointzero_suggestion(5, suggest_onepointzero, version), + _comment_noblock(suggest_onepointzero ? 6 : 5), + "", ) return result end @@ -214,17 +230,16 @@ function comment_text_fail( version::VersionNumber; point_to_slack::Bool=false, ) - reasons_formatted = join(string.("- ", reasons), "\n") + suggest_onepointzero &= version < v"1.0.0" + reasons_formatted = string(join(string.("- ", reasons), "\n"), "\n\n") result = string( - "Your `new version` pull request does not meet ", - "the guidelines for auto-merging. ", - _please_read_these_documents, - "The following guidelines were not met:\n\n", + _comment_bot_intro(1), + _automerge_guidelines_failed_section_title(2), reasons_formatted, - _comment_disclaimer(; point_to_slack=point_to_slack), - _comment_noblock(), - _onepointzero_suggestion(suggest_onepointzero, version), - "\n", + _what_next_if_fail(3; point_to_slack=point_to_slack), + _onepointzero_suggestion(4, suggest_onepointzero, version), + _comment_noblock(suggest_onepointzero ? 5 : 4), + "", ) return result end @@ -258,10 +273,10 @@ function now_utc() return Dates.now(utc) end -function _onepointzero_suggestion(suggest_onepointzero::Bool, version::VersionNumber) +function _onepointzero_suggestion(n, suggest_onepointzero::Bool, version::VersionNumber) if suggest_onepointzero && version < v"1.0.0" result = string( - "\n\n---\n", + "## $n. Declare v1.0?\n\n", "On a separate note, I see that you are registering ", "a release with a version number of the form ", "`v0.X.Y`.\n\n", @@ -272,7 +287,7 @@ function _onepointzero_suggestion(suggest_onepointzero::Bool, version::VersionNu "It's just a recommendation.)\n\n", "If your package does not yet have a stable public ", "API, then of course you are not yet ready to ", - "release version `v1.0.0`.", + "release version `v1.0.0`.\n\n", ) return result else diff --git a/test/automerge-unit.jl b/test/automerge-unit.jl index 2a33968c..c20cd79b 100644 --- a/test/automerge-unit.jl +++ b/test/automerge-unit.jl @@ -45,7 +45,47 @@ function pkgdir_from_depot(depot_path::String, pkg::String) return only_pkdir end +strip_equal(x, y) = strip(x) == strip(y) + +# Here we reference test all the permutations of the AutoMerge comments. +# This allows us to see the diffs in PRs that change the AutoMerge comment. +function comment_reference_test() + for pass in (true, false), + (type_name,type) in (("new_version", AutoMerge.NewVersion()), ("new_package", AutoMerge.NewPackage())), + suggest_onepointzero in (true, false), + # some code depends on above or below v"1" + version in (v"0.1", v"1") + + if pass + for is_jll in (true, false) + name = string("comment", "_pass_", pass, "_type_", type_name, + "_suggest_onepointzero_", suggest_onepointzero, + "_version_", version, "_is_jll_", is_jll) + @test_reference "reference_comments/$name.md" AutoMerge.comment_text_pass(type, suggest_onepointzero, version, is_jll) by=strip_equal + end + else + for point_to_slack in (true, false) + name = string("comment", "_pass_", pass, "_type_", type_name, + "_suggest_onepointzero_", suggest_onepointzero, + "_version_", version, "_point_to_slack_", point_to_slack) + reasons = ["Example guideline failed. Please fix it."] + fail_text = AutoMerge.comment_text_fail(type, reasons, suggest_onepointzero, version; point_to_slack=point_to_slack) + + @test_reference "reference_comments/$name.md" fail_text by=strip_equal + + # `point_to_slack=false` should yield no references to Slack in the text + if !point_to_slack + @test !occursin("slack", fail_text) + end + end + end + end +end + @testset "Utilities" begin + @testset "comment_reference_test" begin + comment_reference_test() + end @testset "`AutoMerge.parse_registry_pkg_info`" begin registry_path = joinpath(DEPOT_PATH[1], "registries", "General") result = AutoMerge.parse_registry_pkg_info(registry_path, "RegistryCI", "1.0.0") @@ -98,18 +138,24 @@ end @test !AutoMerge.meets_name_length("Flux")[1] @test !AutoMerge.meets_name_length("Flux")[1] end - @testset "Name does not include \"julia\" or start with \"Ju\"" begin + @testset "Name does not include \"julia\", start with \"Ju\", or end with \"jl\"" begin @test AutoMerge.meets_julia_name_check("Zygote")[1] @test AutoMerge.meets_julia_name_check("RegistryCI")[1] @test !AutoMerge.meets_julia_name_check("JuRegistryCI")[1] @test !AutoMerge.meets_julia_name_check("ZygoteJulia")[1] @test !AutoMerge.meets_julia_name_check("Zygotejulia")[1] + @test !AutoMerge.meets_julia_name_check("Sortingjl")[1] + @test !AutoMerge.meets_julia_name_check("BananasJL")[1] @test !AutoMerge.meets_julia_name_check("AbcJuLiA")[1] end @testset "Package name is ASCII" begin @test !AutoMerge.meets_name_ascii("ábc")[1] @test AutoMerge.meets_name_ascii("abc")[1] end + @testset "Package name match check" begin + @test AutoMerge.meets_name_match_check("Flux", ["Abc", "Def"])[1] + @test !AutoMerge.meets_name_match_check("Websocket", ["websocket"])[1] + end @testset "Package name distance" begin @test AutoMerge.meets_distance_check("Flux", ["Abc", "Def"])[1] @test !AutoMerge.meets_distance_check("Flux", ["FIux", "Abc", "Def"])[1] diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md new file mode 100644 index 00000000..dfdf70b8 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md @@ -0,0 +1,24 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md new file mode 100644 index 00000000..28a39bbe --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md @@ -0,0 +1,24 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md new file mode 100644 index 00000000..dfdf70b8 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md @@ -0,0 +1,24 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md new file mode 100644 index 00000000..28a39bbe --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md @@ -0,0 +1,24 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md new file mode 100644 index 00000000..0a5610de --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md @@ -0,0 +1,32 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 5. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 6. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md new file mode 100644 index 00000000..41d0b66d --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md @@ -0,0 +1,32 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 5. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 6. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md new file mode 100644 index 00000000..dfdf70b8 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md @@ -0,0 +1,24 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md new file mode 100644 index 00000000..28a39bbe --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_package_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md @@ -0,0 +1,24 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 4. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md new file mode 100644 index 00000000..dc540f13 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_false.md @@ -0,0 +1,20 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md new file mode 100644 index 00000000..f1615d8e --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_0.1.0_point_to_slack_true.md @@ -0,0 +1,20 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md new file mode 100644 index 00000000..dc540f13 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_false.md @@ -0,0 +1,20 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md new file mode 100644 index 00000000..f1615d8e --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_false_version_1.0.0_point_to_slack_true.md @@ -0,0 +1,20 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md new file mode 100644 index 00000000..305d8232 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_false.md @@ -0,0 +1,28 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 4. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md new file mode 100644 index 00000000..a1f2cc71 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_0.1.0_point_to_slack_true.md @@ -0,0 +1,28 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 4. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md new file mode 100644 index 00000000..dc540f13 --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_false.md @@ -0,0 +1,20 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md new file mode 100644 index 00000000..f1615d8e --- /dev/null +++ b/test/reference_comments/comment_pass_false_type_new_version_suggest_onepointzero_true_version_1.0.0_point_to_slack_true.md @@ -0,0 +1,20 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) which are not met + +- Example guideline failed. Please fix it. + +## 3. What to do next + +1. Please try to update your package to conform to these guidelines. The [General registry's README](https://github.com/JuliaRegistries/General/blob/master/README.md) has an FAQ that can help figure out how to do so. You can also leave a comment on this PR (and include `[noblock]`) or send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. Include a link to this pull request if you do so! +2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your `Project.toml` file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number). + +If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the `#pkg-registration` channel in the [public Julia Slack](https://julialang.org/slack/) to ask for help. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_0.1.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_0.1.0_is_jll_false.md new file mode 100644 index 00000000..591cf137 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_0.1.0_is_jll_false.md @@ -0,0 +1,17 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_0.1.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_0.1.0_is_jll_true.md new file mode 100644 index 00000000..37aa3a47 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_0.1.0_is_jll_true.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new `_jll` package registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_1.0.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_1.0.0_is_jll_false.md new file mode 100644 index 00000000..591cf137 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_1.0.0_is_jll_false.md @@ -0,0 +1,17 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_1.0.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_1.0.0_is_jll_true.md new file mode 100644 index 00000000..37aa3a47 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_false_version_1.0.0_is_jll_true.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new `_jll` package registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_0.1.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_0.1.0_is_jll_false.md new file mode 100644 index 00000000..9bc3157d --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_0.1.0_is_jll_false.md @@ -0,0 +1,25 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. + +## 4. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 5. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_0.1.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_0.1.0_is_jll_true.md new file mode 100644 index 00000000..c4a0765b --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_0.1.0_is_jll_true.md @@ -0,0 +1,21 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new `_jll` package registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_1.0.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_1.0.0_is_jll_false.md new file mode 100644 index 00000000..591cf137 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_1.0.0_is_jll_false.md @@ -0,0 +1,17 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. New package registration + +Since you are registering a new package, please make sure that you have read the [package naming guidelines](https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1). + +## 3. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_1.0.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_1.0.0_is_jll_true.md new file mode 100644 index 00000000..37aa3a47 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_package_suggest_onepointzero_true_version_1.0.0_is_jll_true.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new `_jll` package registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_0.1.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_0.1.0_is_jll_false.md new file mode 100644 index 00000000..c68b3a8d --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_0.1.0_is_jll_false.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_0.1.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_0.1.0_is_jll_true.md new file mode 100644 index 00000000..c68b3a8d --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_0.1.0_is_jll_true.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_1.0.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_1.0.0_is_jll_false.md new file mode 100644 index 00000000..c68b3a8d --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_1.0.0_is_jll_false.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_1.0.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_1.0.0_is_jll_true.md new file mode 100644 index 00000000..c68b3a8d --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_false_version_1.0.0_is_jll_true.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_0.1.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_0.1.0_is_jll_false.md new file mode 100644 index 00000000..2b9632a0 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_0.1.0_is_jll_false.md @@ -0,0 +1,21 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_0.1.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_0.1.0_is_jll_true.md new file mode 100644 index 00000000..2b9632a0 --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_0.1.0_is_jll_true.md @@ -0,0 +1,21 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. Declare v1.0? + +On a separate note, I see that you are registering a release with a version number of the form `v0.X.Y`. + +Does your package have a stable public API? If so, then it's time for you to register version `v1.0.0` of your package. (This is not a requirement. It's just a recommendation.) + +If your package does not yet have a stable public API, then of course you are not yet ready to release version `v1.0.0`. + +## 4. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_1.0.0_is_jll_false.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_1.0.0_is_jll_false.md new file mode 100644 index 00000000..c68b3a8d --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_1.0.0_is_jll_false.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_1.0.0_is_jll_true.md b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_1.0.0_is_jll_true.md new file mode 100644 index 00000000..c68b3a8d --- /dev/null +++ b/test/reference_comments/comment_pass_true_type_new_version_suggest_onepointzero_true_version_1.0.0_is_jll_true.md @@ -0,0 +1,13 @@ +## 1. Introduction + +Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of [AutoMerge guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/). Meeting these guidelines is only required for the pull request to be **merged automatically**. However, it is **strongly recommended** to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human. + +## 2. [AutoMerge Guidelines](https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/) are all met! + +Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. + +## 3. To pause or stop registration + +If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text `[noblock]` in your comment. You can edit blocking comments, adding `[noblock]` to them in order to unblock auto-merging. + + diff --git a/test/runtests.jl b/test/runtests.jl index 00878980..c829b0a1 100644 --- a/test/runtests.jl +++ b/test/runtests.jl @@ -7,6 +7,7 @@ using Printf using RegistryCI using Test using TimeZones +using ReferenceTests const AutoMerge = RegistryCI.AutoMerge