Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nc seal post #31

Merged
merged 28 commits into from
Jun 19, 2024
Merged

nc seal post #31

merged 28 commits into from
Jun 19, 2024

Conversation

tdhock
Copy link
Contributor

@tdhock tdhock commented Jun 12, 2024

Seal of Approval Checklist

  • [ x] I have copied the article template folder, renamed it appropriately, and filled in all sections. See this article for an example.

  • [x ] I am the maintainer this package.

OR

  • I have emailed the maintainer and cc'ed [email protected], making them aware that I am submitting this article.

Categories:

The relationship between this package and data.table is best described as:

  • An extension package: Adds to the internal functionality of data.table

  • [ x] An application package: Uses data.table to accomplish a particular task or analysis.

  • A bridge package: Translates data.table syntax to different syntax or provides helper functions for transitioning between data.table and another object type.

  • A partner package: Not necessarily directly connected to data.table, but deliberately follows the core philosophies of data.table

Message for maintainers

If your package is accepted by The Raft, it will be passed along to the data.table developer team for final approval.

Would you like to pass along any information or messages directly to the team along with your blog post?

Hi Kelly, I was not sure about the classification.
I don't think nc "Adds to the internal functionality of data.table" -- but what package would? Can you think of an example? real/existing already or theoretical?
Perhaps nc is an application package? What do you think?

Dev-do not edit

Review request @kellybodwin

slackline and others added 28 commits October 21, 2023 09:12
This adds a `.github/workflows/publish.yaml` for publishing pushes to the `main` branch automatically.

For this to work though I think you need to run `quarto publish` locally first, selecting `GitHub Pages` and letting it
create and push the `gh-pages` branch. The settings on GitHub then need changing, there are two possible places that you
need to check...

1. _Settings > Actions > General > Workflow permissions_ should have _Read and write permissions_ selected. This allows
  the workflow to read from the `main` branch and write to `gh-pages` branch.
2. _Settings > Pages_ probably need changing the _Source_ should be _Deploy from a branch_ and the _Branch_ should be
`gh-pages` and the directory should be `/ (root)`.
…seal-of-approval

Nevermind, only works with Azure
Switch to github action for publishing.
@kbodwin
Copy link
Contributor

kbodwin commented Jun 19, 2024

Thanks Toby! I think this would be an extension package - it's not accomplishing something in a particular data domain, but rather, making it easier to create data.table objects. I'll try to clarify those categories a bit more. Otherwise looks great!

@kbodwin kbodwin changed the base branch from main to dev June 19, 2024 22:46
@kbodwin kbodwin merged commit a69e1f1 into rdatatable-community:dev Jun 19, 2024
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.

3 participants