You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As opposed to blogs, all pages in books or Carpentries lessons are expected to change somewhat regularly.
While discussing with a colleague yesterday (@avallecam), we considered the idea of automatically opening pull requests with automated translation for new content every time something is pushed to main.
Is it something you already considered as well? Are there potential downsides or pitfalls (besides the fact one would need to be careful to group their commits to main)? Would this be a good feature for babeldown, or an adjacent package?
The text was updated successfully, but these errors were encountered:
This is an excellent idea and something that has been on our TODO list for quite a while ropensci/dev_guide#813 However, we think it'd make more sense in PRs (opening PRs to the PR).
Do you want to have a short call to discuss this in the next weeks?
As opposed to blogs, all pages in books or Carpentries lessons are expected to change somewhat regularly.
While discussing with a colleague yesterday (
@avallecam
), we considered the idea of automatically opening pull requests with automated translation for new content every time something is pushed tomain
.Is it something you already considered as well? Are there potential downsides or pitfalls (besides the fact one would need to be careful to group their commits to main)? Would this be a good feature for babeldown, or an adjacent package?
The text was updated successfully, but these errors were encountered: