sassoftware / sassoftware/sas-copilot

Codegen signature

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
12
Forks
1
Avg merge
4m
Merged PRs (30d)
1

Description

Is your feature request related to a problem? Please describe.

To alleviate concerns over trust and governance in Gen AI and code generation, I'd like to have options to track the provenance of generated code.

Describe the solution you'd like

I'd like to have the option for adding a "signature" to comment-generated code by automatically including

"- original codegen via SAS Viya Copilot"

or similar text to the comment used to generate (if accepted) code.

The 'original' in the signature above is to highlight the possibility that even though accepted, the code might have been modified by the user. Organisations may make it user responsibility / establish practices to change the signature in such a case.

Describe alternatives you've considered

There might be other places to add this signature, either at overall program level (in docstring at top). Or this could be a general toggle / option at the extension level too.

Additional context
Having a code signature is also a good way of "advertising" SAS Viya Copilot. However, we might also like to think about what happens when generated code is edited ('improved / refined') or removed later on. Would like to see and participate in discussion on the same.

Reporter's Organization
SAS - GTP

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or code-generation entry point. First map where accepted generated code is handled and document the competing signature locations and editing rules; done requires an agreed, testable design for when signatures are added, changed, or omitted.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.