Yeah, to be totally honest, I already thought we did this! 😅 This is the intended behavior, so we'll need to fix that. Thanks for reporting!

Originally posted by @simskij in containrrr/watchtower#647 (reply in thread)

Summary

#6369 tracks the user who created the build (either manual trigger or rerun) and also tweaked the api/v1/user endpoint to contain a new display_user_id field. The new field should be used to show the user in the top bar, since it reflects the same value that Concourse tracks as the build creator.

We should be able to replace [this function](https://github.com/concourse/concour

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

Hi all 👋

We already released the addon-framework where we want to provide out-of the box integrations with third party tools. It would be super helpful if someone familiar with Microsoft Teams could assist on building the Teams integration.

We have already written the integration for Slack, and relevant code for this is:

• [slack.js](https://github.com/Unleash/unleash/blob/master/lib

Environment

Liquibase Version: 3.8.0, 4.1.1

Liquibase Integration & Version: CLI

Database Vendor & Version: Postgress

Operating System Type & Version: Linux

Description

The Liquibase CLI has the "validate" command to check is a changelog

The TOC on the right hand side of https://toolkit.fluxcd.io/guides/helm-operator-migration/ is very crowded, let's add a mini-TOC at the top of the document to provide links to:

• discussion of breaking changes
• api spec changes
• migration strategy
• FAQ

I was thinking that we could extract the eslint config file into his own module so that we can easily reuse this across any OC related repo in the form of eslint extends.

This because we now have the @opencomponents organization and quite few repos, and i

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

What happened:

Pipeline list view shows jobs listed in alphabetical order by default. This does not provide visibility into the actual ordering of jobs.

What you expected to happen:

Default ordering should follow the following rules.

1. List jobs by the level order in workflow graph. If multiple jobs in same level, list them alphabetically.
2. For disconnected job nodes, eac