Repository FAQ for AIQ

Repository

FAQ for AIQ

HowThis longFAQ answers common questions about AIQ repositories used for test assets, data files, evidence, and integration payloads. Keep answers aligned with the repository configuration and troubleshooting articles to avoid duplicate guidance.

Common questions

• Which repository type should I keepuse? aPrefer non-mastersecure branch?repository

What should I do after I merge a branch?

What if I have conflicts on merge, how do I resolve them?

How often should I merge?

How many changes should I make in a working branch before merging?

What if we need multiple versions of scripts because we have to run against multiple versions of our software?

When GIT is failing, what are the things to consider?

A nonexistent user (username) is cloning a Repository

How long should I keep a non-master branch?

You should keep a non-master branch only until it has been merged to the master and tested there. Once you’ve verified it works, you can get rid of it. Often a checkbox exists for a merge request which will auto-purge the branch should the pipeline triggered build succeed.

What should I do after I merge a branch?

After merging a branch, you should verify the changes are working on the parent branch and delete the feature branch.

What if I have conflicts on merge, how do I resolve them?

With test scripts, often changes from multiple users cannot be merged, or the flow of the script may no longer work as expected. You will have to use a Diff tool and/or review the conflict in the script editor,types such as SFTP, S3, HTTPS, or customer-approved managed storage.

Can repositories store sensitive data? Only when the Testcustomer Designerhas IDE,approved the storage location, encryption, access controls, and chooseretention whichpolicy.What scriptcredentials toshould keep,be used? Use dedicated service identities, roles, or howsecured tocredentials updatewith least privilege.How should cleanup work? Define retention and cleanup rules before high-volume executions create many artifacts.How are issues diagnosed? Check connectivity, credentials, permissions, paths, file names, and repository logs first.

Maintenance note

Consolidate repeated setup steps into the scriptspecific torepository-type articles and keep both changes should that make sense. Most of the time this requiresFAQ manualfocused investigationon decision points and resolution.operational answers.

How often should I merge?

You should merge whenever the “feature” you are working on a feature branch is deemed complete and successfully tested. Keep in mind, the smaller the changes, additions, or a number of areas impacted are easier it is to troubleshoot where new failures exist instead of many changes.

How many changes should I make in a working branch before merging?

As many changes as needed until the “feature” is deemed complete.

What if we need multiple versions of scripts because we have to run against multiple versions of our software?

We recommend you create separate environment branches and create the feature branches below those.

A nonexistent user (username) is cloning a Repository

When using SSH Key the server (Git server) internally will accept any username. All credentials information is inside the SSH file itself