clarkbw

8 ms·

31.
by clarkbw 5y ago
Yes, most people in this situation liquidate them. Dual US / Canadian citizen here living in Canada. While you can keep a TFSA around you'll end up paying taxes on the gains back to the states as well you need to file additional p
32.
by clarkbw 5y ago
> ... make it possible to select a pg database based on async or sync replication Can you explain why you doing this? Is this application data vs. time-series?
33.
by clarkbw 5y ago
Keeping them updated as the code changes is difficult. I’m finding as docs are separate repos disconnected from the source. Not sure how to easily keep it all in sync
34.
by clarkbw 6y ago
Data transfer between GHCR and Actions is free. We're building out a much tighter integration between your source code and the artifacts created. The effects of this will create a stronger supply chain link and work toward better repro
35.
by clarkbw 6y ago
Bandwidth between all GitHub Packages services (GHCR included) is free.
36.
by clarkbw 6y ago
We'll be revising our free storage model in the future to accommodate more open source usage. There are a lot of base layer images people use that are built on GitHub and should be freely available. Those base images should become part
37.
by clarkbw 6y ago
Apologies for that. :( I hope you'll give this a try. GHCR is based off an all new code stack. You'll notice that now you need to associate Containers and the repositories they come from instead of publishing "into repositor
38.
by clarkbw 6y ago
We (the GitHub Packages team where I work) are working on a fix for this and a number of issues with the current docker service. You can join the beta too, details here https://github.com/containerd/containerd/issu
39.
Swift Package Registry Spec(forums.swift.org)
2 points by clarkbw 6y ago|0 comments
40.
by clarkbw 6y ago
x-linking to insights discussion https://news.ycombinator.com/item?id=23092966
41.
by clarkbw 6y ago
Codespaces discussion happening over here https://news.ycombinator.com/item?id=23092904
42.
by clarkbw 7y ago
Yes, we (internally) call this a "Bill of Health" and believe that all packages should have this kind of diff-able information available. Understanding what's happening at the source level is key to being able to trust any p
43.
by clarkbw 7y ago
Yes thank you! We believe namespaces are a good thing and will continue to promote it as best practice. Hopefully we can integrate repository information to packages meta data such that you could be aware of a change of ownership even for
44.
by clarkbw 7y ago
The post covers this. > Later this year, we will enable npm’s paying customers to move their private npm packages to GitHub Packages—allowing npm to exclusively focus on being a great public registry for JavaScript. Packages will continu
45.
by clarkbw 7y ago
Part of GitHub (I work at GitHub and lead the Packages team)
46.
by clarkbw 7y ago
Private repos aren't scanned and if we did offer the service to scan private repos we would only ever contact the repo owners and not the service providers. In the case of public repos we're in a race against time where bad actor
47.
by clarkbw 7y ago
We use this at GitHub to power the commit token scanning. It is very fast and handles multiple regexes at once. We are looking for secrets from multiple providers. Couldn’t find a better option for this type of usage.
48.
by clarkbw 7y ago
Sorry you've been fighting this. We're actively working on the documentation as well as improving the setup workflows for Actions which should alleviate lots of this pain. Those one line snippets are likely going to be taken down,
49.
by clarkbw 8y ago
There are a couple of other attributes that can be useful from Linguist. The vendored can help maintain your language stats which show up on your repo page and in GH/explore. For rails you could add something like this so all the JS yo
50.
Ignore white space in code review(blog.github.com)
3 points by clarkbw 8y ago|1 comments
51.
Require multiple reviewers for pull requests(blog.github.com)
80 points by clarkbw 9y ago|34 comments
52.
by clarkbw 9y ago
There goes any hope of the HomeKit support promise coming through in the Ring Pro.
53.
by clarkbw 9y ago
The linked article about the problems with battery storage is from 2011 and battery technology continues to change at a rapid pace that couldn’t have been predicted then. The article uses lead acid as the example of cheapest batteries that
54.
by clarkbw 9y ago
A switcher is under consideration but we're focused on some other (what we believe are) more important aspects right now and wanted to get this part out the door quickly for people to start using. I wouldn't consider a switcher im
55.
by clarkbw 9y ago
You can leave the last S for off (for savings) if you want /ISSUE_TEMPLATE(S)/ or /PULL_REQUEST_TEMPLATE(S)/
56.
Multiple issue and pull request templates(github.com)
17 points by clarkbw 9y ago|7 comments
57.
by clarkbw 9y ago
As Firefox moves to WebExtensions all these debugging tools should become just as available. Currently it is difficult for extension authors to support Firefox as well but that is changing. React DevTools is about to convert. Redux alread
58.
by clarkbw 9y ago
This is going to get a whole lot better. Try nightly now to see what's coming.
59.
How the debugger.html got into the flow(jasonlaster.github.io)
1 points by clarkbw 10y ago|0 comments
60.
by clarkbw 10y ago
Thanks for all your hard work! If you want to check out the new model of development take a look at the debugger, its the first in series of new panels coming to Firefox. https://github.com/devtools-html/debugger.html

More ›