Closed SwiftySalmon closed 2 months ago
See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.
OR
To have the bot accept them for you, reply quoting the following line: @check-spelling-bot apply updates.
See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.
OR
To have the bot accept them for you, reply quoting the following line: @check-spelling-bot apply updates.
@check-spelling-bot apply updates.
@check-spelling-bot apply updates.
See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.
pcs Postcodesio recordlinkage
OR
To have the bot accept them for you, reply quoting the following line: @check-spelling-bot apply updates.
See the :open_file_folder: files view, the :scroll:action log, or :memo: job summary for details.
:x: Errors | Count |
---|---|
:information_source: candidate-pattern | 1 |
:x: ignored-expect-variant | 3 |
See :x: Event descriptions for more information.
Hey, not sure why I've randomly received notifications about this PR :shrug:
I noticed you'd removed me and others from the DESCRIPTION - The usual practice is to have a single person as the 'package maintainer' they get the role cre
(creator) - in the case of this package I put PHS as this which wouldn't be ok on CRAN but I think is fine...
For everyone else, small contributions would be 'contributor' ctb
and bigger contributions should be 'authors' aut
. People can have as many roles as required.
See the phsmethods DESCRIPTION and these docs - https://r-pkgs.org/description.html#sec-description-authors-at-r
remove some packages from description file that don't get used anywhere