Global ETD Search

Search theses and dissertations gathered from participating repositories worldwide. Every result links back to the library that holds it. No account is needed.

Results

Showing 1 to 20 of 449 for “"Commits"”.

  1. Unfolding the Rationale for Code Commits

    … history is to search for the rationale for code commits. Existing work found that developers report that rationale is one of the most important aspects to understand code changes and that it can be quite difficult to find. While this finding strongly points out the fact that understanding the …

    vt Repository record for Unfolding the Rationale for Code Commits (opens in a new tab)

  2. A Qualitative Study of Vulnerability-Fixing Commits

    … research team, which contains security fixing commits related to open source Java projects used by SAP and manually curated and validated by their researchers. We study a statistically significant sample of those commits. In particular, we collect information from the related repositories, …

    concordia Download PDF for A Qualitative Study of Vulnerability-Fixing Commits (opens in a new tab)

  3. Merge-Trees: Visualizing the integration of commits into Linux

    … that help answer questions about how commits are integrated into the project. Older versions of the kernel are used in a variety of systems where it is impractical to update to the current version of the kernel. Some of these applications include the controllers for spacecrafts, the …

    uvic Repository record for Merge-Trees: Visualizing the integration of commits into Linux (opens in a new tab)

  4. The experience of the therapist when a patient commits suicide

    <p>Therapists who work with severely disturbed individuals will likely experience the suicide of a patient. The purpose of this study was to describe this experience using phenomenological methods of reduction. Eleven therapists participated in an audiotaped interview of between one to two hours in …

    utk-theses Repository record for The experience of the therapist when a patient commits suicide (opens in a new tab)

  5. Investigating completeness and consistency of links between issues and commits

    Software developers use commits to track source code changes made to a project, and to allow multiple developers to make changes simultaneously. To ensure that the commits can be traced to the issues that describe the work to be performed, developers typically add the identifier of the issue to the …

    ubc Repository record for Investigating completeness and consistency of links between issues and commits (opens in a new tab) Download PDF for Investigating completeness and consistency of links between issues and commits (opens in a new tab)

  6. Exploiting Token and Path-based Representations of Code for Identifying Security-Relevant Commits

    … treating the identification of security-relevant commits as a classification task. Since existing literature on neural networks for commit classification is sparse, we first turn to document classification for inspiration. Extensive research in this domain, on the other hand, has resulted in …

    waterloo Repository record for Exploiting Token and Path-based Representations of Code for Identifying Security-Relevant Commits (opens in a new tab)

  7. Zhangfei suppresses the growth of Medulloblastoma cells and commits them to programmed cell death

    Medulloblastoma cells do not contain detectable amounts of the bZIP protein Zhangfei. However, previous work has shown that expression of this protein in cells of the ONS-76 line, derived from a human medulloblastoma, causes the cells to stop growing and develop processes that resemble neuritis (a …

    sask Repository record for Zhangfei suppresses the growth of Medulloblastoma cells and commits them to programmed cell death (opens in a new tab)

  8. WarningsGuru - Analysing historical commits, augmenting software bug prediction models with warnings and a user study

    … historical change measures to predict bugs in commits at a higher level. We developed a tool which combines both of these approaches. Our tool analyses each commit of a project and identifies which commit introduced a warning. It processed over 45k commits, more then previous research. We …

    concordia Download PDF for WarningsGuru - Analysing historical commits, augmenting software bug prediction models with warnings and a user study (opens in a new tab)

  9. Investigating the Techniques to Detect and Reduce Bug Inducing Commits During Change Operations in Software Systems

    … as possible. Early detection of bug inducing commits is a challenge. We have conducted three studies in this thesis with the goal of detecting bug inducing (inconsistent) commits as soon as those are made and minimizing the occurrences of such commits. In our first two studies, we apply …

    sask Repository record for Investigating the Techniques to Detect and Reduce Bug Inducing Commits During Change Operations in Software Systems (opens in a new tab)

  10. Who commits what? An evaluation of offenders convicted of domestic violence and sexual abuse in Iowa

    <p>The purpose of this analysis is to evaluate the criminal histories of a cohort of offenders in Iowa who have been newly admitted to prison on a most serious domestic or sex offense. Moreover, addressing whether offenders convicted of domestic violence and sex abuse have intersecting, …

    iastate Repository record for Who commits what? An evaluation of offenders convicted of domestic violence and sexual abuse in Iowa (opens in a new tab)

  11. An empirical investigation on the prevalence, impact, and manifestation of rework commits in the merge requests mechanism

    … of our industrial partner by looking at rework commits in the submitted merge requests (MR) to detect possible issues earlier in their CI/CD pipeline. The emerging research questions are studied for this purpose: RQ1.: What is the distribution of rework commits across MR at Kaloom? RQ2.: How …

    ets-quebec Download PDF for An empirical investigation on the prevalence, impact, and manifestation of rework commits in the merge requests mechanism (opens in a new tab)

  12. Mining energy – aware commits: exploring changes performed by open – source developers to impact the energy consumption of software systems

    … by exploring a set of software changes, i.e., commits, to obtain insights into actual solutions implemented by open source developers when dealing with energy consumption. We use as our main data source GITHUB, a source code hosting platform for collaborative development, and extract a sample …

    brazil-ufpe Repository record for Mining energy – aware commits: exploring changes performed by open – source developers to impact the energy consumption of software systems (opens in a new tab)

  13. Exploring the Usefulness of Version Control Information for Program Comprehension

    … projects. Our analysis showed that 66.9% of commits are not helpful for understanding concerns and only 19.5% are very helpful. This result implies that it can be time consuming for programmers to find relevant commits when reviewing a concern history and motivates the need for tool support …

    calgary Repository record for Exploring the Usefulness of Version Control Information for Program Comprehension (opens in a new tab)

  14. Reducing the cognitive and temporal costs of software history exploration

    Software developers traverse several commits and issues from issue tracking systems when exploring software revision history to answer questions about the rationale behind presently written code. Existing tools impose a cognitive burden on developers as developers must sift through many commits and …

    ubc Repository record for Reducing the cognitive and temporal costs of software history exploration (opens in a new tab) Download PDF for Reducing the cognitive and temporal costs of software history exploration (opens in a new tab)

  15. Avaliação da contribuição de desenvolvedores para projetos de software usando mineração de repositórios de software e mineração de processos

    … through three different perspectives: (i) buggy commits; (ii) the size of commits; and (iii) the most important bugs. For the opensource project 12.827 commits and 8.410 bugs have been analyzed while 4.663 commits and 1.898 bugs have been analyzed for the commercial project. Our results indicate …

    brazil-ufrn Repository record for Avaliação da contribuição de desenvolvedores para projetos de software usando mineração de repositórios de software e mineração de processos (opens in a new tab)

  16. Studying the Use of SZZ with Non-functional bugs

    … models that focus on identifying defect-prone commits, referred to as \emph{Just-In-Time (JIT) Quality Assurance} are known to be useful in allowing developers to review risky commits. JIT models, however, leverage the SZZ approach to identify whether or not a past change is bug-inducing. …

    concordia Download PDF for Studying the Use of SZZ with Non-functional bugs (opens in a new tab)

  17. Commit Patterns and Threats to Validity in Analysis of Open Source Software Repositories

    … interest, we discovered a pattern of monolithic commits in the SourceForge community. Consequently, we also report on the effects that this pattern of commits can have when using SourceForge as a data-source for temporal analysis of open source projects or for studies of individual developers.

    byu Repository record for Commit Patterns and Threats to Validity in Analysis of Open Source Software Repositories (opens in a new tab) Download PDF for Commit Patterns and Threats to Validity in Analysis of Open Source Software Repositories (opens in a new tab)

  18. Taxonomy of Software Readability Changes

    … a manual review of software readability commits to identify what changes developers tend to make. In this study, we identified 1,782 potential readability commits for 800 open-source Java projects, by mining keyword patterns in commit messages. These commits were then reviewed by human …

    rit Repository record for Taxonomy of Software Readability Changes (opens in a new tab)

  19. Change Impact Analysis of Code Clones

    … a solution to minimize the effects of atypical commits (extra large commits) on the accuracy of the detection of evolutionary coupling. We propose a clustering-based technique to split atypical commits into pseudo-commits of related entities. This considerably reduces the number of incorrect …

    sask Repository record for Change Impact Analysis of Code Clones (opens in a new tab)

  20. An automated approach for performance deviation analysis of evolving software systems

    … automatizada de revelar fontes potenciais – commits e issues – de variação de desempenho em cenários durante a evolução de sistemas de software. A abordagem define quatro fases: (i) preparação – escolher os cenários e preparar os releases alvos; (ii) análise dinâmica – determinar o desempenho …

    brazil-ufrn Repository record for An automated approach for performance deviation analysis of evolving software systems (opens in a new tab)

Page 1 of 23