@User do you factor in GH issue 👍 s when prioritising changes? Super interested in your workflow

https://github.com/dendronhq/dendron/pull/449 <- CI! I'd really appreciate it if you could take a look through the tests skipped in the "skip leaky tests" commit so I can rebase that out -- I just couldn't grok what was wrong with those

(process) @User would you prefer to get bug report in

feedback

vs

questions

channels, or directly as

issues

on github?

was looking forward to this pr all week 🙂 i might be underwater today but if not today, definitely by tomorrow!

the typical lifecycle is for reports to start off in questions and then end up in issues 😅

this also gives other people a chance to chime in

Sorry about that, between my estimates and the elasticity of time during lockdown I am hopeless 🤯

you rdoing great in terms of software estimates, all things considered 🙂

yes I do. I don't have a great workflow for this yet - its mostly me looking at most recent issues and making sure they are all triaged and responded to. at the end of the week, i take inventory, close issues that were resolved, add comments, etc. definitely could use improvement and additional eyes so thanks @User @User , and @User for the offer. i will think about this and post more on this later this week. also open to suggestions if y'all have seen good working models elsewhere

Well first of all I plan to add labels to all the templates at least the type and a triage needed so that those that are still needing triage can be directly filtered Pr for that should come in shortly. Secondly I would propose adding the Github Action [labeler](see: https://github.com/actions/labeler) (which i can do) to apply some labels to the Pull requests based on the changed files. Like adding the area.{*} label it affects based on the packages that get modified. Thirdly I'm a fan of synced Gitkraken boards, which I would like to use, but thats something only the repo admin can set up.

First open source project I'm being part of and what we do at my day job is embarassingly unstructured and impromptu so I don't have anything immediate to suggest

don't you worry at work we only started to learn as well

Devs want to introduce a lot of things but we don't really have technical guidance and boss aint a fan of 'all those fancy startup culture bs' 😄 we are just some clueless overworked devs flailing to meet what IR promised the investors.

Must.. resist... ranting. I'll stop here

so its not quite gitkraken but dendron has a zenhub board: https://app.zenhub.com/workspaces/dendron-5f06937cfa4f3b001d5673c9/board?repos=274724694 its a mirror of github issues on a kanban board happy to give people access to it. currently items are sorted by

current/next/later/q&a/blocked

the labeler looks cool. does it also applie to issues? we get 10x the amount of issues vs pull request so that's the area that some automation would help

Sadly the labler only works for PRs

yeah I know Zenhub didn't even notice it at first

I’m sure we could write something that could do this, the API is pretty sane

Was my thought, but based on what are the labels getting choosen

Not directly Dendron-related, but can we just appreciate for a moment how delightful the GraphQL documentation is? Those code blocks are all editable, it's such a sweet tutorial

been meaning to find an opportunity to use graphql in a project. just so familiar with REST that its hard to justify switching

also, WE HAVE CI/CD TESTS NOW! https://github.com/dendronhq/dendron/runs/1698416891 thanks @User for doing the ground work on this 🥳

Gatsby was my very light introduction to graphql 😄

yeah, I think that was my first exposure to it as well 🙂

it was such an overkill for what I was trying to do (personal website)

I think I want to port it to 11ty at some point.

if anyone has windows and would like to do a little QA, i have a mission for you 😇 I need you to initialize a new dendron workspace, select "empty repository" when prompted, and then run the following at your workspace root (same folder where dendron.code-workspace file is)

npm init -y
npm install --save @dendronhq/dendron-cli@latest
npm install --save @dendronhq/dendron-11ty@1.24.4
dendron-cli buildSiteV2 --wsRoot .  --stage dev --serve

if this is successful, you should be able to visit

localhost:8080

and see the following welcome please react with a ☑️ if you were able to do this successfully or a 💥 otherwise (with details of the error you saw)

Kosher to execute those commands in WSL?