vergissberlin / autopilot-jira-proxy Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 361 KB

Create tickets in Jira with autopilot webhooks

TypeScript 90.16% Dockerfile 9.84%

autopilot-jira-proxy's Introduction

Hi there, I'm André - aka vergissberlin 👋

I'm a father, developer, and teacher!

🌱 I am currently immersing myself in the depths of LoRaWAN.
👯 I’m looking to collaborate with other developers and ux experts.
🥅 2024 goals: Improve skills on Dart and Azure.
⚡ Fun fact: Siegmud Jähn was my neighbor!

🌧️ I'm a Senior Cloud Engineer having expertise in

📀 With Hands on experience working with data stores like

📚 Frameworks I've worked with

🔭 And some useful tools like

📦 Checkout some of my packages published on

💁‍♂️ Connect with me

📊 This week I spent my time on

Other                         16 hrs 1 min    ██████████████▒░░░░░░░░░░   57.66 %
Dart                          8 hrs 33 mins   ███████▓░░░░░░░░░░░░░░░░░   30.82 %
JSON                          1 hr 28 mins    █▒░░░░░░░░░░░░░░░░░░░░░░░   05.28 %
YAML                          50 mins         ▓░░░░░░░░░░░░░░░░░░░░░░░░   03.04 %
Makefile                      19 mins         ▒░░░░░░░░░░░░░░░░░░░░░░░░   01.15 %

📺 Latest YouTube Videos

📕 Latest Blog Posts

Medium

Hashnode

Stack Overflow

Answer by André Lademann for It is possible to login the user into chrome extension using the local storage of our website?

TTN LoRaWAN network Leipzig

Work experience

gantt
	dateFormat YYYY-MM-DD
	title      Work experience André Lademann

	section Feelancer 
		NULLzuEINS Inh. André Lademann  :done,  nze, 2007-03, 2023-03-01
		click nze href "https://nullzueins.com"
	
	section Angestellter
		Topedo Leipzig :done, emp1, 2007-03-01, 2008-02-01
		Freelancer     :done, emp2, after emp1, 2011-08-01
		Digitalwert    :done, emp3, after emp2, 2013-03-01
		Falk Anayltics :done, emp4, after emp3, 2013-09-01
		Netresearch    :done, emp5, after emp4, 2023-02-28
		Thinkport      :active, emp6, after emp5, today
	
		click emp3 href "https://torpedo-motor.com"
		click emp3 href "https://digitalwert.de"
		click emp5 href "https://netresearch.de"
		click emp6 href "https://thinkport.digital"

autopilot-jira-proxy's People

Contributors

Watchers

autopilot-jira-proxy's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

CircleCI
Travis CI
Buildkite
CodeShip
Azure Pipelines
TeamCity
Buddy
AppVeyor
But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `12.12.9` to `12.12.10`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build: There are 1 failures, 0 warnings, and 0 notices.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of ts-node is breaking the build 🚨

The devDependency ts-node was updated from `8.5.2` to `8.5.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ build: There are 1 failures, 0 warnings, and 0 notices.

Release Notes for Fix transpile diagnostics

Fixed

Pass correct diagnostics list in transpile mode (#917) 907e3e1
Make --ignore relative ea6e1da

Commits

The new version differs by 3 commits.

30adec7 8.5.3
907e3e1 Pass correct diagnostics list in transpile mode (#917)
ea6e1da Make --ignore relative

See the full diff