Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEAT: Redirect output to another file. #499

Open
eskopp opened this issue Jan 31, 2024 · 1 comment
Open

FEAT: Redirect output to another file. #499

eskopp opened this issue Jan 31, 2024 · 1 comment
Assignees
Labels
Brainstorming Some New Feature to be added with prior proper discussion

Comments

@eskopp
Copy link

eskopp commented Jan 31, 2024

Is your feature request related to a problem? Please describe.
The basic problem is that the workflow looks very good but I'm frustrated that it's so big, so I put it in a linked readme in my special repo. Unfortunately it can`t write to the waka.md.

Describe the solution you'd like
There should be an option to specify with with: in which file the content should be written. Readme.md can be set by default. It would be very helpful for me.

Describe alternatives you've considered
This is not applicable as the feature does not exist. I tried to put the area block in another file and hoped that the workflow would find it. Unfortunately this was not the case.

Additional context
Please :)

Example:

name: Waka Readme

on:
  workflow_dispatch:
  schedule:
    - cron: "0 0 * * *"

jobs:
  update-readme:
    name: Update this repos README
    runs-on: ubuntu-latest
    steps:
      - uses: anmol098/waka-readme-stats@master
        with:
          WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}
          GH_TOKEN: ${{ secrets.GH_TOKEN }}
          SHOW_PROJECTS: "False"
          SHOW_LINES_OF_CODE: "False"
          SHOW_LOC_CHART: "False"
          LOCALE: "en"
          OUTPUT_FILE: "waka.md"
@eskopp eskopp added the Brainstorming Some New Feature to be added with prior proper discussion label Jan 31, 2024
@DavidFrings
Copy link

I had the same Idea so I read the code, and rewrite the part... now I have the Issue #515 ... I can't test it, and I don't want to make a pull request before testing my code...

Can someone help me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Brainstorming Some New Feature to be added with prior proper discussion
Projects
None yet
Development

No branches or pull requests

3 participants