| Geth | Spreadsheet-XLSX: tbrowder++ created pull request #33: Fix README examples |
16:27 | |
| Spreadsheet-XLSX/main: a6892743fa | (Tom Browder)++ | 9 files Fix README examples |
17:04 | ||
| Spreadsheet-XLSX/main: ce9b3356ba | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 9 files Merge pull request #33 from tbrowder/tb-readme Fix README examples |
|||
| tbrowder | thanks! | 17:05 | |
| for my next pr i want to add, in /examples, a script showing how to fill a new xlsx file with the contents of one or more CSV files. what do y’all think about that? support it or shoot it down? | 17:09 | ||
| ok, i'm gonna try it... | 20:04 | ||
| hm, can you release the latest main you merged? i don't think i can with this repo | 20:30 | ||
| ah, i see the new note about releasing. i'll try to do that | 20:54 | ||
| ok, i need help here: where do i release from, my fork? or do i have to login to the github repo online? i vaguely remember i just doing it from my fork | 21:15 | ||
| [Coke] | You should not release from your fork on a community module, you should release *from* the community module's repo | 21:33 | |
| if you release the new repo from a fork, you're either 1) claiming the module going forward, 2) going to make it very hard for the next person who wants to cut a release. | 21:34 | ||
| tbrowder | thank you! that certainly makes sense, ChatGPT has been misleading me. however, it has given me a bash script to help enter the fez password while seeing the characters. tonyo showed me something similar once but i can’t find it. | 22:57 | |
| another question: merge my branch to main first? or not? | 23:00 | ||
| it should already be merged | 23:01 | ||
| so i’m releasing a changed main | 23:02 | ||
| * i will be releasing a changed main for a new version, correct? | 23:13 | ||
| arg, so i do have to do it online, or can i use an “upstream” local repo to release it? | 23:23 | ||
| [Coke] | Clone the raku-community module repo. release from that dir | 23:29 | |
| assuming you're using mi6, then the tags and versions, etc. will end up in the r-c-m/main branch, as intended. | 23:30 | ||
| You could *probably* do the release from yours and figure out how to push everything back upstream... but that seems like way too much work |