Skip to content

Conversation

@Raj-G07
Copy link

@Raj-G07 Raj-G07 commented Sep 25, 2025

Pull Request Template

Description

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Additional Context (Please include any Screenshots/gifs if relevant)

...

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings
  • I have tagged the reviewers in a comment below incase my pull request is ready for a review
  • I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you and congratulations 🎉 for opening your very first pull request in writers-program

@Raj-G07
Copy link
Author

Raj-G07 commented Sep 25, 2025

@Achanandhi-M Set the TOKEN secret in your repository or organization settings. This secret is required for the CLA Assistant GitHub Action to operate correctly

Signed-off-by: Raj Gupta <150777419+Raj-G07@users.noreply.github.com>
@Raj-G07
Copy link
Author

Raj-G07 commented Sep 26, 2025

To fix this, add a TOKEN secret in your repository settings (Settings → Secrets and variables → Actions → New repository secret), and it is a valid GitHub personal access token with permissions.

@Raj-G07

This comment was marked as off-topic.

Copy link
Collaborator

@Achanandhi-M Achanandhi-M left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Raj-G07, thanks for the update! We only need to modify the CLA pipeline, not all the pipeline files.

Signed-off-by: Raj Gupta <150777419+Raj-G07@users.noreply.github.com>
Signed-off-by: Raj Gupta <150777419+Raj-G07@users.noreply.github.com>
This reverts commit cd6fd99.

Signed-off-by: Raj Gupta <150777419+Raj-G07@users.noreply.github.com>
Signed-off-by: Raj Gupta <150777419+Raj-G07@users.noreply.github.com>
Copy link
Member

@amaan-bhati amaan-bhati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Achanandhi-M I think he has updated the pr and removed the updates in all the workflow files, only the cla workflow changes are there, can you please review it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update GitHub CLA Action in Writer’s Program CI/CD pipeline

3 participants