Skip to content

build: rewrite format-suggest action to more be more secure - #71

Closed
BBeltz1 wants to merge 1 commit into
devfrom
build/secure-format-suggest
Closed

build: rewrite format-suggest action to more be more secure#71
BBeltz1 wants to merge 1 commit into
devfrom
build/secure-format-suggest

Conversation

@BBeltz1

@BBeltz1 BBeltz1 commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

Your commits explain the what and where you made changes in the code. Your commit messages explain why you made the commits. You do not need to reiterate this. This PR is meant to address the big picture, Why

Justification

Describe the big picture of your changes here to communicate to the reviewers why they should accept this pull request.
Please describe the importance/impact of the problem and a description of how the changes in this pull request will address, resolve or improve the problem.
If it fixes a bug or resolves a feature request, be sure to link to the issue below

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist/Reminders

Put an x in the boxes that apply

  • I have updated relevant documentation? (run pkgdown::build_site() to check)
  • I have created unit tests and run devtools::test() to ensure all unit tests pass locally?
  • I have run devtools::check() to ensure package builds locally?
  • I have followed the proposed CONTRIBUTING guideline?

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Reviewer instructions:

Assign at least 2 reviewers:

  • one of which should be a maintainer,
  • the others should be familiar with the subject changes.

Please detail the process reviewers will need to follow to properly test these changes. It is especially helpful to identify the exact code needed to conduct a local build/review/test and to specify any aspects of the testing that may not be obvious.

Formatting

This repo contains an air.toml file that automatically formats code to a set of standards.
It is preferred that contributors and reviewers install the air formatting tool.

@BBeltz1 BBeltz1 closed this Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant