A QR code encoder in as3
jbpin/express-marionette-boilerplate 4
Quick setup with example to start an express + marionette project. Use browserify and grunt watch.
class util to use NativeProcess API
A simple Javascript/Node library to find the closest point of my current location given a set of point.
Signals is a new approach for AS3 events, inspired by C# events and signals/slots in Qt.
Repo for minimalist reproduction of issue with antd / less next@9
☎️ Nextcloud Android library
jbpin/android_device_samsung_gtaxlwifi 0
TWRP device tree for Samsung Galaxy Tab A 10.1 WiFi (2016 Exynos)
🌈 A UI Design Language
Android client SDK for communicating with OAuth 2.0 and OpenID Connect providers.
starteddungeon-revealer/dungeon-revealer
started time in 7 days
starteddavidkpiano/durable-entities-xstate
started time in 8 days
startediamsrp/dexter
started time in 11 days
startedReactKit/SwiftState
started time in 13 days
push eventgitops-working-group/gitops-working-group-old
commit sha ccce85746ece9cb825691b874bebc634e1bf244b
Add deprecation notice Signed-off-by: Brice Fernandes <brice@weave.works>
push time in 13 days
issue commentgitops-working-group/gitops-working-group-old
All issues now transferred to https://github.com/gitops-working-group/gitops-working-group/
comment created time in 13 days
issue openedfluxcd/gitops-working-group
https://github.com/gitops-working-group/gitops-working-group/ has been created.
There is some content here which can't be easily transferred (PRs, issues), so it might be worth to
- [ ] figure out the best way how folks can indicate they want to be involved in the new repo
- [ ] transfer other ideas/suggestions so they can be picked up by the group
- [ ] change all links to the new repo
- [ ] archive this repo
I started the conversation in https://cloud-native.slack.com/archives/C01G9DEE88M/p1609929228052000 as well. Pinging @dj1k @cdavisafc and @todaywasawesome.
created time in 15 days
issue openedfluxcd/gitops-working-group
The Ambassador Labs team and I are definitely keen to get involved and help in any way we can. A lot of folks from our community have adopted GitOps, and so we can lend our collective learnings from this to the working group (particularly in relation to ingress and service mesh config, and cloud native dev tooling like Telepresence).
We are also keen to help spread the word on GitOps, and see the guidelines/manifesto being a great way to codify and share best practices.
created time in 17 days
startedcodesandbox/codesandbox-client
started time in 21 days
startedjbpin/as3-qrcode-encoder
started time in 24 days
startedricardo-ch/go-kafka-connect
started time in a month
startedyuezk/GlobalProtect-openconnect
started time in a month
startedardera/flutter-pi
started time in a month
startedmozilla/DeepSpeech
started time in a month
startedjpmorganchase/modular
started time in a month
startedhound-search/hound
started time in a month
issue commentfluxcd/gitops-working-group
@scottrigby Scott Rigby any thoughts on this? Tell me in case if it is irrelevant and out of scope ?
comment created time in a month
issue openedfluxcd/gitops-working-group
We have several environment stages at our place but gitops
doesn't cover the promotion part among these stages.
As a workaround we adopted "branch per environment" strategy and rotating the PR to the other environment but these all are manual steps and when we script this to CI system its all non standard i.e different CI system requires different way of doing it for example github actions requires different way of doing it, gitlab plugin different way.
I think it is beneficial to have a standard cli tool something like gitops
which deals with all the manual steps during the gitops deployment process. This tool just interacts with the underlying git tool and wraps the gitops specific git commands.
for example:
gitops init hld --for-app=guestbook
would initiate the HLD repository if not present
gitops env add stage
would create a stage
branch in HLD repository
gitops raisePR prod --from=stage
raises a PR from stage
branch to prod
branch
gitops rollback prod
etc
created time in a month
startedmeyda/meyda
started time in a month
issue openedfluxcd/gitops-working-group
Working Group Work Product Name Suggestion "GitOps Commitments"
There has been some discussion around the use of the word "manifesto" and the connotations that word might bring with it. There was a comment in one of the Google Docs but I can't find it now, and it was brought up during the first meeting of the working group on Dec 10.
I wanted to make a suggestion for a name of the work product of this group:
"GitOps Commitments"
I believe it's a fun name that expresses the intent of the work product of this working group.
created time in a month
push eventfluxcd/gitops-working-group
commit sha 0e7a01b196ff6fd0944164598e83b806bb3f700a
Add Slack info Signed-off-by: Scott Rigby <scott@r6by.com>
commit sha 543e42dedc039898b9cd954846ff16fee4662678
markdownlint Signed-off-by: Scott Rigby <scott@r6by.com>
commit sha 66871ac9fc63f4be6f13406dd1a49ee1e4fd25da
Merge pull request #44 from scottrigby/slack-and-markdownlint Add Slack info
push time in a month
PR merged fluxcd/gitops-working-group
Slack info per call today. Also quick markdownlint.
pr closed time in a month
issue closedfluxcd/gitops-working-group
Discussions were mentioned in the call today.
Seems fitting to enable those on this repo (as opposed to the shared flux discussions), since the intent is to move this repo to a new org.
closed time in a month
scottrigbyissue commentfluxcd/gitops-working-group
Closing as this has been taken care of.
comment created time in a month
issue commentfluxcd/gitops-working-group
Yes it will, because of what @hiddeco just said 👍
comment created time in a month
issue commentfluxcd/gitops-working-group
Given it has been made available to all of our repositories, I think the feature is in public beta now and you no longer have to request and/or be granted access to it on a per repository basis.
comment created time in a month
issue commentfluxcd/gitops-working-group
@scottrigby will this migrate when we have it under the sig-app delivery git?
comment created time in a month
issue commentfluxcd/gitops-working-group
See slack chat with @dj1k. Summary is we may want to wait given that we may be able to move this repo within the next few days. OTOH since there were 45 people on the call today, we may want to capture the swell of interest by going ahead and getting that started (they will carry over automatically when the repo is moved).
comment created time in a month