---
title: "Discussion on \"Using GitHub secrets may break job outputs\" | Hashnode"
description: "Discussion on \"Using GitHub secrets may break job outputs\". If you don't want to spend hours debugging GitHub CI jobs, avoid using job outputs that may contain secrets inside. Job outputs will not be passed to dependent jobs if they contain secrets in any part of output value.\nThere is a tiny note about this ..."
url: "https://hashnode.com/posts/using-github-secrets-may-break-job-outputs/66c22c3031095a39a0f8bfa1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Using GitHub secrets may break job outputs](https://piotrekkr.hashnode.dev/using-github-secrets-may-break-job-outputs?utm_source=hashnode&utm_medium=feed)

If you don't want to spend hours debugging GitHub CI jobs, avoid using job outputs that may contain secrets inside. Job outputs will not be passed to dependent jobs if they contain secrets in any part of output value. There is a tiny note about this ...

Aug 18, 2024 · 2 min read · piotrekkr.hashnode.dev  
Read the article

-   [#github](https://hashnode.com/tag/github)
-   [#secrets](https://hashnode.com/tag/secrets)
-   [#ci-cd](https://hashnode.com/tag/ci-cd)

## Written by

[Piotrekkr](https://hashnode.com/@piotrekkr)

@piotrekkr

  
[View profile](https://hashnode.com/@piotrekkr)

Previously software engineer, currently working as DevOps engineer.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
